After setting up the Firebase integration with PagerDuty, your Firebase project allows PagerDuty to page your on-call responders in response to events reported by Crashlytics, like new, regressed, or increasing-velocity issues.
Set up the PagerDuty integration in the Firebase console
- Sign in to the Firebase console, then select your project.
- Click
, then select Project Settings. Select the Integrations tab.
- On the PagerDuty integration card, click Install.
- Follow the on-screen instructions to set up the integration.
- Click Verify & save.
Configure alert settings
The console lets you configure alerts by app and event type. For example, you can turn off alerts in your testing app or route alerts about different apps to different PagerDuty projects.
Event types
The Firebase integration with PagerDuty allows you to send alerts in response to four event types:
- New issues: triggered when your app experiences a crash that Crashlytics hasn't seen before.
- New non-fatal issues: triggered when your app experiences a non-fatal issue that Crashlytics hasn't seen before.
- Regressed issues: triggered when your app experiences a crash that you'd previously marked closed.
- 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.
Configure settings for each app
Here's how to configure alerts for your project, including selecting specific PagerDuty services for each alert type:
- Sign in to the Firebase console, then select your project.
- Click
- Go to the Crashlytics alerts card. Select the app you want to configure from the dropdown menu.
- Select the PagerDuty service where you want to send alerts for this app.
- For each type of alert, select from the dropdown whether you want to send that type of alert to PagerDuty.
- Repeat these steps for each app that you want to configure.
That's it! Firebase will post bugs to your specified PagerDuty service if your apps have new, regressed, or increasing-velocity issues.