Firebase: Budget and Daily Spending Limit - firebase

I've set a daily spending limit for my Firebase project.
Inside the same project, I added a NodeJS App Engine app.
So I've received this warning:
In that case, all spending limits are ignored?
If Firebase goes to $99999 it won't be stopped?
Thanks..

The warning you receives reflects reality, if your app is deployed in the App Engine Flexible environment. To avoid $99999 surprises, you can create a budget for a GCP project to protect somehow your bill and monitor all of your Google Cloud Platform charges from one place. To see how you create a budget, you may have a look at the "Managing GCP Projects, App Engine Applications, and Billing" documentation page.

Related

See Firebase Test Lab Usage

Normally, you can see under "Usage and billing" the usage of all Firebase Services. We have integrated integration test with Firebase Test Lab into our CI. Now I want to know how much usage we use and when do we need to pay for our usage.
Is there any view in Firebase or Google Cloud Platform to the use Firebase Test Lab usage of the current project?
It appears you are currently using the Firebase Spark free tier? On that plan you may run tests on 10 virtual devices and 5 physical devices each day.
If you're using the Blaze pay-as-you-go plan, you can see Test Lab device usage in the Cloud Console. Start at https://console.cloud.google.com/billing and select your project and billing plan. From there you can view usage graphs and generate billing reports.

Firebase: Enable the Google Cloud Build API for your Cloud Functions project?

Hi I am using firebase and the firebase functions.
1 day ago I received an email from Google Cloud with the following content:
Starting April 20, 2020, Cloud Functions will use Google Cloud Build, Container Registry, and Google Cloud Storage to build and store your source code, and deploy container image(s) before running them on Google Cloud. You must enable the Cloud Build API for your project(s) to ensure your Cloud Function is built and deployed correctly. Once you enable the API, you may incur charges if your Cloud Build, Container Registry, or Cloud Storage usage exceeds the free tier limits for these products. You can find a list of your projects that are using Cloud Functions and may be affected by this change at the bottom of this email.
I tend to avoid tinkering the Google Cloud (or even logging in there) as I am using the Firebase as an all inclusive solution and so far I did not have the need to login there.
Now the question:
Do I need to follow the instructions and take action, or is this something separate from the Firebase Functions?
The "affected" project that is mentioned on the email is the Firebase project
To be able to use cloud functions after April 20, 2020 you must enable the Cloud Build API because this will be a new deployment framework.
You will not be able to use cloud functions if you do not enable the Cloud Build API after this date.
These changes will apply even for Firebase cloud functions.
I believe you will need to do it only if you are going to deploy Cloud Functions in the future, Cloud Functions already deployed will not be affected.
In case you are worried about billing, Cloud Build provides a free tier where only usage above 120 build-minutes/day will be charged. When your usage is within the free tier, you will not be charged for the Cloud Build portion of Cloud Function deployments. See Cloud Build pricing for more information.
Similarly, Cloud Storage and Container Registry share a free tier where only usage above 5GB-months will be charged. ( * Note : free tier only limited to US regions - US-WEST1, US-CENTRAL1, and US-EAST1 and aggregated over all 3 regions )​ For example, if you have a large deployment that uses 100GB of storage, you will only be charged an additional $2.47 for storage/month (based on these particular U.S. regional storage prices).
You can monitor your usage and see whether you are getting close to hitting the free quotas.
This is a best effort from Google to communicate information that is necessary to the user’s continued use of the product or that is considered a necessary legal update and keep customers away from having future issues
Using Cloud Build, Container Registry and Cloud Storage provides the following benefits:
Detailed function build logs will be available in the GCP Console, aiding in debugging and increasing visibility.
The ability to get build time that exceeds the current build quota of 120 build-mins/day.
The ability to view a built container image for your function in Container Registry.

Stripe Payment Using Firebase Cloud Funtions Pricing for Live App React Naive

i have implemented Stripe payment gateway using Firebase Cloud Functions in react native. When i test it locally it's worked perfect. payment succeeds but when i go live url , payment can't process due to outbound networking
You can't integrate with Stripe using Cloud Functions on the free
plan, because that plan has a limitation where it's not able to make
outgoing connections to endpoints that are not fully controlled by
Google. This is set in place in order to prevent abuse. You will have
to provide billing information and upgrade to a paid plan.
My Question to Firebase Users is that as a company:
How much i have to pay for this per/month or per year ?
Also is this secure or not ?
And From where i can pay Firebase to able to process live url.
The cost of Cloud Functions is purely based on how much you use it, not on the time period that you use it. For full details I recommend studying the Firebase pricing page, and use the calculator at the bottom of that page. But you can get started without paying, as the Blaze plan has the same free quota that you on the free Spark plan. You'll only start paying for Firebase usage when you go beyond that free quota.
You can upgrade (and later downgrade) your project to the paid plan from the pricing page, or by clicking the upgrade link at the bottom left of your Firebase console.

Firestore reads - inconsistency between App Engine Quota and Firebase Console

I started using Firestore recently (Free plan) in my iOS app, the app is in Production now, and I see huge discrepancy in the number of Reads. App Engine Quota shows 1M reads of 0.05M (free quota) (Cloud Firestore Read Operations), while Firebase Console (Database tab) shows just a one hundred reads for today - 10,000 times difference!
The app can still read the data from the servers (it's not from cache as I tried to delete the app and reinstall), so the Firestore functionality is not limited by exceeding the free quota.
Each app user can read only one document (via listener) with applied security rules, and it reads own document only 3-5 times per session. There are about 50 users so far, so the expected number of reads matches Firebase console.
Is there a known bug in App Engine console?
Is there a way or free tool to understand the source of all those reads?
Which reporting tool is more reliable in general - Firebase Console or App Engine Console?
I appreciate your help guys!

Is there a Firebase API endpoint to fetch account usage?

I'm building a SAAS project on Firebase and weighing the pros and cons of multi-tenant architecture vs managed Firebase instances for each account.
One of the key challenges with managed instances is reporting usage. I've searched through Firebase docs but have not been able to find an API endpoint to fetch a Firebase project's account usage (eg bandwidth, function invocations, storage, etc).
Is there a API that I'm missing or is this alternatively possible with core Google Cloud APIs?
firebaser here
We just added a REST API to manage projects and the apps in those projects. But there is currently no way to report usage for a project across all Firebase products. It sounds like a useful feature through, so I recommend filing a feature request.
Until a feature is added that fits your needs, you will have to do the tracking from within your own app, or by proxying the tracked functionality through Cloud Functions, where you can then log whatever you need for tracking usage.

Resources