With Firebase's PagerDuty integration, PagerDuty can page your on-call responders in response to Firebase events like new or regressed issues in Crashlytics.
Set up a PagerDuty integration
To set up a PagerDuty integration, click Install on the PagerDuty card on the Integrations page of the Firebase Console.
Follow the instructions on that page to complete the integration.
Configure per-app settings
The console lets you configure alerts by app and event type. For example, you can turn off notifications in your testing app or route notifications about different apps to different PagerDuty projects.
Firebase's PagerDuty integration currently allows you to send alerts in response to four event types:
- New Crashlytics issues: triggered when your app experiences a crash Crashlytics hasn't seen before.
- New Crashlytics non-fatal issues: triggered when your app experiences a non-fatal issue Crashlytics hasn't seen before.
- Regressed Crashlytics issues: triggered when your app experiences a crash that you'd previously marked closed.
- Increasing Crash Velocity issues: triggered when a single crash type affects 1% of sessions in a 60 minute period for a given app version.
By default, Firebase only sends alerts to PagerDuty for Increasing Crash Velocity issuess. You can configure other alerts on the Firebase Console's Integrations page:
- In the Firebase Console, navigate to Integrations.
- Click Manage on the PagerDuty integration card.
- Find the app you want notifications for, and click Edit.
- If you have multiple PagerDuty services, use the PagerDuty service for this app dropdown to select which one you'd like to use.
- Check or uncheck the box next to each alert type to determine which Crashlytics events trigger PagerDuty alerts.
- Click Save.