Crashlytics custom alerts
Crashlytics velocity alerting mechanism is very basic and it unfortunately generates a lot of false positive alerts. Support more advanced alarm settings
Tahsin Dane
shared this idea
-
Cyril Findeling commented
we're getting hundreds of useless alerts and missing important ones, %age and # of affected users threshold are really necessary
-
Sahar Weissman commented
currently since we cannot customize the alert parameters - e.g. min users count to trigger - we're getting multiple "false positives" alerts where for ex. a single user with multiple issues (crashes) can trigger the alert.
configuring the # of min. users (and maybe other parameters) can help us in reducing this "noise".
thanks. -
Eran Lunenfeld commented
We are encountering a high number of false positive alerts, typically caused by one device experiencing multiple crashes and triggering a velocity alert
-
Gal Koren commented
+1, We are experiencing a lot of false-positives on every version release, usually due to a single device that experiences multiple crashes and triggers a velocity alert. Letting a single device alert the entire dev team like that just makes no sense.
Adding a minimal *fixed* number of affected users (not just percentage) to the velocity alert settings can really assist us here. Thanks!