[null,null,["最后更新时间 (UTC):2025-08-12。"],[],[],null,["\u003cbr /\u003e\n\nUse velocity alerts to notify your team when any individual issue is causing an\nurgent problem in your app. For Crashlytics, an issue is a grouping of\nsimilar crashes or application not responding (ANR) events.\n| **Important:** To get velocity alerts, **make sure your app uses *at minimum* the following versions of the\n| Crashlytics SDK:** \n| Apple platforms: v10.8.0+ \\| Android: v18.6.0+ (BoM v32.6.0+) \\| Flutter: v3.4.5+ \\| Unity: 11.7.0+\n\nWhat triggers an alert?\n\nVelocity alerts are triggered when an issue in your app crosses certain\nthresholds that you\n[configure in the Firebase console](#configure-thresholds).\n\nYou define the threshold for velocity alerts in terms of a\n***percentage of users and the minimum number of users that were\nimpacted by the crash or ANR***. You can set the percentage threshold value\nbetween 0% and 100% of sessions. The minimum users threshold can be set to any\nnumber greater than or equal to 10. By default, the velocity alert threshold is\nset at 1% of sessions and 25 users.\n\nSpecifically, an alert is triggered if, during a 30-minute time period,\n***all*** the following are true:\n\n- An issue in an app exceeds the defined percentage threshold and exceeds the minimum users set for that app.\n- The app has at least 10 users in that time period.\n- There was no alert previously raised for the issue in the app on that version.\n\nConfigure velocity alert thresholds\n\nTo configure velocity alert thresholds, you must have the\n`firebasecrashlytics.config.update` permission. The following roles include\nthis required permission by default:\n[Firebase Crashlytics Admin](/docs/projects/iam/roles-predefined-product#crashlytics),\n[Firebase Quality Admin](/docs/projects/iam/roles-predefined-category#quality_roles),\n[Firebase Admin](/docs/projects/iam/roles-predefined-all-products), or\nproject [Owner or Editor](/docs/projects/iam/roles-basic).\n\nConfigure velocity alert thresholds for each of your registered apps. Each app\ncan have a different alert threshold.\n\n1. Sign in to the Firebase console, then select your project.\n\n2. Click settings, then select\n **Project Settings** . Select the\n [**Alerts** tab](https://console.firebase.google.com/project/_/settings/alerts).\n\n3. Go to the **Crashlytics** alerts card and select the **Velocity Alerts**\n tab.\n\n4. Configure the alert thresholds for the app.\n\nReceive alerts\n\nGet default alerts\n\nBy default, Firebase can send Crashlytics alerts using email. For velocity\nalerts and regressions, Firebase can also show these alerts in the\nFirebase console.\n\nTo receive Crashlytics alerts using this default mechanism, you must have\nthe `firebase.projects.update` permission. The following roles include this\nrequired permission by default:\n[Firebase Admin](/docs/projects/iam/roles-predefined-all-products) or project\n[Owner or Editor](/docs/projects/iam/roles-basic).\n\nBy default, every project member (who has the required permissions to receive\nalerts) will get an email when an alert from Crashlytics is triggered.\n\nTurn alerts on or off for your own account\n\nFor your own account, you can turn Crashlytics alerts on or off without\naffecting other project members. Note that you still need the required\npermissions to receive alerts.\n\n1. Sign in to the Firebase console, then select your project.\n\n2. Click settings, then select\n **Project Settings** . Select the\n [**Alerts** tab](https://console.firebase.google.com/project/_/settings/alerts).\n\n3. Go to the **Crashlytics** alerts card and select the **Velocity Alerts**\n tab.\n\n4. Set your account preference for Crashlytics alerts.\n\nSet up basic alerting to third-party services\n\nFor Crashlytics alerts, Firebase offers a mechanism to send alerts to the\nfollowing third-party services:\n[Slack](https://support.google.com/firebase/answer/9005934),\n[Jira](https://support.google.com/firebase/answer/9118259), or\n[PagerDuty](https://support.google.com/firebase/answer/9168499).\n\n1. Set up these basic alerting options using guided workflows in the\n [*Integrations* tab](https://console.firebase.google.com/project/_/settings/integrations/)\n in your settings *Project\n settings*.\n\n2. Select which configuration is used for individual apps and configure the\n destination of other alerts on the Crashlytics card of the\n [*Alerts tab*](https://console.firebase.google.com/project/_/settings/alerts)\n in your settings *Project settings*.\n\nNote that if you want more control and customization for sending alerts to any\nthird-party service (not limited to only Slack, Jira, or PagerDuty), check out\nthe [Set up advanced alerting to third-party services](#advanced-alerts-3p)\nsection that describes advanced alerting options.\n\nSet up advanced alerting to third-party services\n\nYou can send Crashlytics alerts to your team's preferred notification\nchannel, using Cloud Functions for Firebase. For example, you can write a function\nthat captures an alert event for velocity alerts and posts the alert information\nto a third-party service, like Discord, Slack, or Jira. With this advanced\nalerting mechanism, you can fully customize the information sent to the\nthird-party service; for example, you can include helpful deep-links into the\nFirebase console or add company-specific troubleshooting information.\n| **Note:** To use advanced alerting capabilities, your Firebase project needs to use the [Blaze pricing plan](/pricing).\n\nTo set up advanced alerting capabilities using Cloud Functions for Firebase, follow these steps:\n\n1. [Set up Cloud Functions for Firebase](/docs/functions/get-started),\n which includes the following tasks:\n\n 1. Set up a development environment for Node.js or Python.\n 2. Install and sign into the Firebase CLI.\n 3. Initialize Cloud Functions for Firebase using the Firebase CLI.\n2. [Write and deploy a function](/docs/functions/alert-events) that\n captures an alert event from Crashlytics and handles the event\n payload (for example, posts the alert information in a message on Discord).\n\nTo learn about all the Crashlytics alert events that you can capture, go to\nthe reference documentation for\n[Crashlytics alerts](/docs/reference/functions/2nd-gen/node/firebase-functions.alerts.crashlytics)."]]