I'm happy to announce that symbolicated stacks and signatures for crash pings are now available in BigQuery. This makes it easy to e.g. write queries to analyze the stability of Firefox (and Fenix!). You can even do interesting things like comparing with telemetry.socorro_crash to determine under-reported crash signatures. This query, created by :gcp, shows top crashers and their trends.
The data is available in the moz-fx-data-shared-prod.crash_ping_ingest_external.ingest_output table, which can be joined using document_id and submission_timestamp with crash views such as fenix.crash and firefox_desktop.desktop_crashes. The table has a lag time of a few hours past UTC midnight: ingestion runs at 2:00 UTC on the prior day's data and usually takes 1-2 hours. Data has been back-filled through 2024-09-01.
We symbolicate all nightly and beta crash pings. Release crash pings are randomly sampled, selecting about 5000 crash pings per (os, process-type) combination.
The availability of this data allows us to easily use telemetry rather than reports for determining top-crashers, automatically creating new bugs, etc:
Please direct questions to the #crashreporting matrix channel (or directly to me, by replying to this email or otherwise).
-Alex