Use velocity alerts to notify your team when any individual issue is causing an urgent problem in your app. For Crashlytics, an issue is a grouping of similar crashes.
What triggers an alert?
Velocity alerts are triggered when an issue in your app crosses a threshold that you define in the Firebase console.
You define the threshold for velocity alerts in terms of a percentage of user sessions that were impacted by a crash. Refer to Google Analytics documentation to learn more about sessions. You can set a threshold value between 0.1% and 1% of sessions. By default, the velocity alert threshold is set at 1% of sessions.
Specifically, an alert is triggered if, during a one-hour time period, the following are true:
- An issue in an app exceeds the defined threshold for that app.
- The app has 250 sessions in that time period.
- There was no alert previously raised for the issue in the app.
Update the alert threshold
To update velocity alerts, you must have the
permission. The following roles include this required permission by default:
Firebase Crashlytics Admin,
Firebase Quality Admin,
Firebase Admin, or
project Owner or Editor.
Configure a velocity alert threshold for each of your registered apps. Each app can have a different alert threshold.
- In the Firebase console, go to your Crashlytics dashboard.
- At the top of the page, select an app from the app dropdown list.
- In the top bar of the Issues pane, open the overflow menu ( ), then select Velocity alert settings.
- Follow the on-screen instructions to configure the alert threshold for the app.
In the Firebase console, you can set up how to route velocity alerts to yourself or your team:
Email or Firebase console alerts
Set your preferences for receiving Crashlytics alerts via your account's Firebase alert subscriptions (in the top right corner, go to
> Firebase alerts ) Settings