---
title: "Unlock custom observability by exporting Crashlytics data to Cloud Logging"
description: "This new integration allows you to export your Crashlytics data, including fatal crashes, non-fatals, and ANRs, directly into Google Cloud Observability."
published: "2026-01-30"
last_updated: "2026-01-30"
authors:
  - "Ernan Anguiano (Outbound Product Manager)"
  - "Andrew Brook (Software Engineer)"
categories:
  - "Crashlytics"
  - "Cloud Observability"
  - "Android"
  - "iOS"
  - "Cloud Logging"
  - "Cloud Monitoring"
canonical_url: "https://firebase.blog/posts/2026/01/crashlytics-export-cloud-logging"
---

# Unlock custom observability by exporting Crashlytics data to Cloud Logging

*Published January 30, 2026 by Ernan Anguiano (Outbound Product Manager), Andrew Brook (Software Engineer)*

---
We know that maintaining app stability is critical to any app’s success. The Crashlytics dashboard is the daily go-to for thousands of developers to track crash-free metrics and velocity, but wouldn't it be nice if there were a way to dive even deeper into that data?

That's why we’re excited to announce that you can now export Crashlytics data, including fatal crashes, non-fatals, and ANRs, to Cloud Logging!

This new integration with Cloud Logging opens up the Google Cloud Observability suite of powerful tools for developers and SREs who need comprehensive observability and advanced monitoring, alongside deeper diagnostic capabilities. For example, you can perform advanced queries, build specialized dashboards for unique user journeys, unify your crash data with server logs, or trigger tailored alerts based on the specific thresholds your team requires.

Here is what you can do with this new integration:

### Create custom alerts for your workflow

While Crashlytics provides default velocity alerts, we heard your requests for custom alerts – and Cloud Observability takes your incident response to an enterprise level. Want to notify your on-call team only if a specific non-fatal error spikes in a specific region? You can now create a log-based metric for that specific error and set an alert policy that triggers only when it crosses your defined threshold. This ensures specific teams are notified only when it matters most, reducing alert fatigue.

By exporting to Cloud Logging, you can use **Cloud Monitoring** to set up advanced alerting policies with custom thresholds, SQL, PromQL, and log-based metrics. By routing your crash data through Google Cloud, you unlock additional notification channels beyond **Jira, PagerDuty, Slack, and email**—including **SMS, Webhooks, Pub/Sub, and [more](https://docs.cloud.google.com/monitoring/support/notification-options#creating_channels).**

### Advanced querying and filtering

Sometimes you need to find a needle in a haystack. The **Logs Explorer** allows you to run complex queries using the Logging Query Language (LQL) to filter raw crash data, while **Logs Analytics** allows you to query logs using familiar SQL.

For example, you can search for crashes occurring only on a specific device model or filter by [custom keys](https://firebase.google.com/docs/crashlytics/customize-crash-reports#add-keys) you’ve set up in your app. You can also use **Gemini** directly in the Cloud console to help you write these queries if you aren't familiar with LQL yet!

### Visualize trends with custom dashboards

Every team monitors stability differently. With your data in Cloud Logging, you can build **custom dashboards in Cloud Monitoring**.

You can visualize crash-free rates, session volumes, and error counts in a single view, or even monitor crashes on critical user journeys, like your crashes at checkout on your ecommerce app. If you choose to enable the export of **Firebase sessions data** alongside your crashes, you can gain even deeper context into user sessions and crash-free metrics.

### Unified logging: client meets server

One of the hardest parts of debugging is correlating what happened on the user's device with what happened on your backend. Previously, this data was siloed.

With this export, your Crashlytics data lives alongside your server logs in Cloud Logging. You can now query your logs to see exactly what was happening on your servers at the precise moment a client-side crash occurred, giving you a full-stack view of the error.

### How to get started

Setting up this integration is easy and can be done directly from the **Firebase console**:

1. Navigate to **Project Settings \> [Integrations](https://console.firebase.google.com/u/0/project/_/settings/integrations)**.  
2. Find the **Cloud Logging** card, and click **Link**.  
3. Follow the on-screen prompts. You’ll have the option to include Firebase sessions data for richer metrics.

> **Note**: Cloud Logging offers a free tier of 50GB per month per project, which is sufficient for many apps. Beyond that, standard Cloud Logging pricing applies.

### What’s Next?

We built this feature to bridge the gap between mobile stability tracking and comprehensive observability. We can’t wait to see how you use these tools to build more stable, reliable apps.

Check out the [documentation](https://firebase.google.com/docs/crashlytics/cloud-logging-export) for a deep dive on setting up log-based metrics and alerts. If you have any feature requests or feedback, check out our [User Voice](https://firebase.uservoice.com/).