You can export your Firebase Crashlytics data into Cloud Logging. Once the data is exported, it's also available to the full Google Cloud Observability Suite, where you can filter your logs, build custom dashboards, set up custom alerts, and even export the data to other services. Check out What can you do with your data? for a comprehensive list and examples for working with data stored in Cloud Logging.
This page describes how to set up export of Crashlytics and (optionally) Firebase sessions data into Cloud Logging.
Set up export to Cloud Logging
In the Firebase console, go to the Integrations page.
In the Cloud Logging card, click Link.
Follow the on-screen instructions to set up export to Cloud Logging, including the following options:
(Enabled by default) To improve understanding of crash-free metrics, enable Firebase sessions data export.
Choose which apps will export logs.
If you already have one or more active apps, the linking workflow displays an estimated data usage level for logs from each of your apps. This value is estimated based on the volume of Crashlytics data from the previous 30 days.
This option can also be enabled during the initial setup of export to Cloud Logging.
In the Firebase console, go to the Integrations page.
In the Cloud Logging card, click Manage.
Select the Include sessions checkbox.
This action enables export of session data for all of your linked apps.
Unlink from Cloud Logging
Unlinking from Cloud Logging stops any new logs from being exported.
Be aware of the following:
Any data already exported into Cloud Logging will persist for the allowed retention time, and storage charges may still apply. You can manually delete your logs to prevent any further billing.
If you have Cloud Logging data stored in other services (like BigQuery), that data might be governed by different terms for data persistence.
You can unlink from Cloud Logging at the Firebase project level, at the Crashlytics product-level, or at the app-level.
Here's how to unlink from Cloud Logging:
In the Firebase console, go to the Integrations page.
In the Cloud Logging card, click Manage.
Choose to unlink Crashlytics entirely or to unlink a specific app.
To unlink your Firebase project entirely, find the button at the bottom of the page.
When prompted, confirm that you want to stop exports.
What happens after you enable export?
View logs for any new events within a few minutes of Crashlytics receiving the event.
Monitor your data usage levels:
View the data usage level for logs from your linked apps in the Cloud Logging integration card in the Firebase console.
View your current and previous month's data usage in the Logs Storage page in the Google Cloud console.
Quotas and pricing
Cloud Logging offers a no-cost level of usage per month (per project). The usage can be from any Google or Firebase product using Cloud Logging. You can upgrade your project to the pay-as-you-go Blaze pricing plan to unlock additional paid usage and features. Learn more about pricing for Cloud Logging.
You can monitor and manage Cloud Logging and billing:
Estimate your Cloud Logging bills using the Google Cloud Pricing Calculator.
Throttle logs by creating exclusion filters for log sinks.
Set up alerts to help control costs.
Logs are automatically deleted after 30 days, with the option to set custom retention.
Note that the log entry for a particular request or event may be delayed or, in rare cases, dropped. While logs can be used to understand requests or events, they may not reflect the true usage that appears in your project usage and billing.
What's next?
Learn how to filter your logs to view specific information and costs for data storage and further analysis.
View and build log-based metrics, then use these metrics in Cloud Monitoring to do any of the following:
Learn about the log schema for exported data.