Blog
Reading Crash Spikes After Deploy
How to tell a release-related quality issue from background noise in application analytics.
Crash and error rates often wobble with traffic. Tie spikes to version cohorts and to devices or OS versions that received the build first.
Look for new stack traces, not only higher counts of familiar ones. A familiar error that suddenly concentrates on the new version still matters—but a novel signature is a louder alarm.
Pair quality signals with adoption. A tiny cohort on a canary build can look catastrophic in relative rates while absolute impact remains small—or the reverse.