Read first
Each week starts with a real crash export (redacted). You annotate before we talk. Crash Analytics Monitoring is a reading skill before it is a tooling skill.
Easington Lane studio · Crash Analytics Monitoring
A crash is a story. Most queues stop at the first frame.
Service Craftcore trains engineers and support leads to treat Crash Analytics Monitoring as editorial work: fingerprints, breadcrumbs, and the decision to page — or to wait for the next build.
Flagship programme
Crash Grouping Studio
Eight evenings on how Crash Analytics Monitoring actually behaves once a release hits mixed devices. You leave with a written grouping charter, not a slide deck of vendor screenshots.
Open the studio syllabus
What people actually said after week four
I used to reopen the same NullPointer as three tickets because the message differed by locale. The grouping charter from Crash Grouping Studio made that embarrassing, in a useful way.
The symbol-map night shift module is slower than a recorded webinar. That is the point. I still wish the homework dumps were smaller — our CI artefacts are heavy — but the ANR versus crash split stuck.
How the studio runs
Argue the fingerprint
We compare grouping rules in pairs. If two people would page different owners, the rule is not finished.
Write the charter
You leave with a one-page document your on-call rota can actually use on a Sunday in GB traffic.
What this teaching is for
- Fewer duplicate incidents You learn to collapse stacks that look unique only because of line noise or obfuscation.
- Release gates that mean something Crash-free sessions become a conversation with product, not a vanity tile.
- On-call that sleeps Breadcrumbs get a budget. Not every fatal event deserves a 03:00 ping.
- Vendor-agnostic habits We use Crash Analytics Monitoring ideas that survive a tool change next quarter.
Recent notes
Fingerprint before you page
Why the first matching frame is a poor paging key once ProGuard has been through the build.
Breadcrumbs that lie
Navigation trails that look causal and are only chronological.
Native versus JS crash queues
Two pipelines, one on-call, and the merge rules that actually hold.
If you want the syllabus rather than the essays, the studio list is the shortest path. Questions go to contact.