신속 알림 기준은 비정상 종료 또는 ANR의 영향을 받은 사용자의 비율 및 최소 사용자 수로 정의됩니다. 백분율 기준값은 세션의 0%에서 100% 사이로 설정할 수 있습니다. 최소 사용자 기준은 10 이상의 숫자로 설정할 수 있습니다. 기본적으로 신속 알림 기준은 세션의 1% 및 사용자 25명으로 설정됩니다.
특히 30분 동안 다음 조건이 모두 충족되면 알림이 트리거됩니다.
앱에 발생한 문제가 정의된 백분율 기준을 초과하고 해당 앱에 설정된 최소 사용자 수를 초과합니다.
Crashlytics 알림의 경우 Firebase는 Slack, Jira 또는 PagerDuty 등의 서드 파티 서비스에 알림을 전송하는 메커니즘을 제공합니다.
settings프로젝트 설정의 통합 탭에서 단계별 워크플로를 사용하여 이러한 기본 알림 옵션을 설정합니다.
개별 앱에 사용되는 구성을 선택하고 settings프로젝트 설정의 알림 탭에 있는 Crashlytics 카드에서 다른 알림의 대상을 구성합니다.
타사 서비스(Slack, Jira 또는 PagerDuty에만 국한되지 않음)로 알림을 전송하는 데 더 많은 제어와 맞춤설정이 필요하면 고급 알림 옵션을 설명하는 타사 서비스에 대한 고급 알림 설정 섹션을 참조하세요.
서드 파티 서비스에 대한 고급 알림 설정
Cloud Functions for Firebase를 사용하여 Crashlytics 알림을 팀의 기본 알림 채널로 보낼 수 있습니다. 예를 들어 신속 알림을 위한 알림 이벤트를 캡처하고 Discord, Slack 또는 Jira와 같은 타사 서비스에 알림 정보를 게시하는 함수를 작성할 수 있습니다. 이 고급 알림 메커니즘을 사용하면 타사 서비스로 전송되는 정보를 완전히 맞춤설정할 수 있습니다. 예를 들어 유용한 딥 링크를 Firebase Console에 포함하거나 회사별 문제 해결 정보를 추가할 수 있습니다.
Cloud Functions for Firebase를 사용하여 고급 알림 기능을 설정하려면 다음 단계를 수행합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],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)."]]
