After I migrated my app to console.firebase.google.com I cannot view the database usage quota, bandwidth usage and several other statistics in the firebase.com analytics tab. Is there any way to check this using new panel?
Update: you can now see your project's Realtime Database, Cloud Storage, and Hosting usage in the Firebase console.
Update (20160727): you can now see your project's database usage from the Firebase Console. Thanks for your patience!
Previous answer: the database usage quota charts are not yet available in the new Firebase Console. We're working on adding them, as well as adding similar charts for Storage and Hosting. Hang in there!
I see a new Usage tab now. Console > Database > Usage
Currently shows Sent Bytes, Storage and Connections. Looks like it may not be stable yet, because it does not match the stats reflected in my billing section.
Related
is there any way in firebase or google cloud console to view the firestore document reads by source (admin or web sdk)? we had a massive spike and need this info to triage.
All options are listed on the documentation page on monitoring usage, but there is no view of what specific document caused the spike in reads. If you want such a thing, you'll have to build it yourself - which unfortunately won't help for this incident that has already occurred.
I have an app which uses firebase storage and I am observing an unusual traffic to the storage. The bandwidth usage is unusually high, which shouldn't happen with the usual behavior of the app.
I need to isolate a user or a stored file which causes this unusual bandwidth usage. Is there any way I can get more information about the storage usage, other than the information shown at the Usage tab of firebase console?
Firebase Storage only tracks and shows aggregate data for the usage in your project. It does not tie this usage to specific Firebase Authentication users.
If you need that, consider adding your own tracking for this, for example by logging uploads/downloads to Google Analytics for Firebase.
You can also log to Stack Driver, although it might only be in aggregate there too. For the exact metrics, see the Google Cloud Platform documentation on its storage metrics.
Alternatively you could reach out to Firebase support for personalized help in troubleshooting. But I'm not sure if they have access to the type of data you're looking for.
Is there any API available for getting real-time database usage.
We need to show usage and related info on our dashboard and my client don't want to visite firebase consol and option for the upgrade or downgrade plan programmatically
There is currently no API for this. You may file a feature request here.
I am using Firebase for almost 2 months now for my app in production and right now I am on Spark plan for sometime until I get user base. I see that the Spark pricing allows 1GB of downloads per day and 5GB of total storage but nowhere on the console I am able to see how much storage quota I have used up now. This is really important to a lot of users, if you show usage information for Database you should show it for storage as well.
As long as Storage is concerned it's actually a Google Cloud Storage Bucket, you can visit the Google Cloud Console and see the details. Firebase currently does not show the bucket usage details.
You can send them a feature request from this link :
https://firebase.google.com/support/contact/bugs-features/
Like Raghvendra said, you can view it on the Google Cloud Console at the following link: https://console.cloud.google.com/storage/browser/my-app.appspot.com
my-app will be your project name, and is the same as the one you use on Firebase: https://console.firebase.google.com/project/my-app/storage/my-app.appspot.com/files
Is there any tool to monitor the data transfer to my real time database in firebase? To see how many user connect at live time and how much data is transferred?
There's a usage tab in your Firebase Database console that has most of that information.
We also just released a tool that allows you to profile your database usage. See that tool's blog post and reference documentation.