Alerting options for Crashlytics

Crashlytics offers different alerts and different ways to receive these alerts.

Alerts are based on the following event types:

  • New fatal issues: triggered when your app experiences a crash or ANR that Crashlytics hasn't seen before.

  • New non-fatal issues: triggered when your app experiences a non-fatal issue Crashlytics hasn't seen before.

  • Regressed issues: triggered when your app experiences a crash that you'd previously marked closed.

  • Trending issues: triggered when an issue is emerging or trending.

  • Increasing-velocity issues: triggered when a single crash or ANR type impacts a percentage of users in a 30-minute period for a given app version.

You have the following options for receiving these alerts. Each option allows progressively more configurability and customization.

Alerting by email or in the Firebase console

Firebase can send all Crashlytics alerts to your email. For regressed issues and increasing-velocity issues, Firebase can also show alerts in the Firebase console.

  • Alerts for regressed and trending issues do not require any configuration and are sent by default when you set up Crashlytics.

  • Alerts for new non-fatals, fatals, ANRs, and increasing-velocity issues are not sent by default. To receive these alerts, you must (at minimum) select your preferred alerting channel.

All alert types offer some configuration. For example, you can turn alerts on or off for your own account, and for increasing-velocity issues, you can set thresholds for when alerts are sent. You can view and configure these alerts in the Alerts tab in the Firebase console.

Learn more about alerting by email or in-console

Basic alerting integrations with Slack, Jira, and PagerDuty

Firebase offers basic alerting integrations to send Crashlytics alerts to Slack, Jira, and PagerDuty.

At a high-level, here's how to set up and configure these integrations in the Firebase console:

  1. Follow the guided workflow for each service in the Integrations tab in your Project settings.

  2. Select which configuration is used for individual apps and configure the destination of other alerts on the Crashlytics card of the Alerts tab in your Project settings.

Learn more about basic alerting integrations with Slack, Jira, and PagerDuty

Advanced alerting to other notification channels

You can send Crashlytics alerts to your team's preferred notification channel, using Cloud Functions for Firebase. For example, you can write a function that captures an alert event for velocity alerts and posts the alert information to a third-party service, like Discord, Slack, or Jira. With this advanced alerting mechanism, you can fully customize the information sent to the third-party service; for example, you can include helpful deep-links into the Firebase console or add company-specific troubleshooting information.

To set up advanced alerting capabilities using Cloud Functions for Firebase, follow these steps:

  1. Set up Cloud Functions for Firebase, which includes the following tasks:

    1. Set up a development environment for Node.js or Python.
    2. Install and sign into the Firebase CLI.
    3. Initialize Cloud Functions for Firebase using the Firebase CLI.

  2. Write and deploy a function that captures an alert event from Crashlytics and handles the event payload (for example, posts the alert information in a message on Discord).

To learn about all the Crashlytics alert events that you can capture, go to the reference documentation for Crashlytics alerts.

Learn more about handling alerts using Cloud Functions for Firebase