Great work everyone! This is a big milestone in a multi-year journey to level-up our stability infrastructure. Thanks to everyone involved along the way for getting us here.
On Wed, Dec 11, 2024 at 7:14 AM 'Alex Franchuk' via dev-platform@mozilla.org <dev-platform@mozilla.org> wrote: > I’m announcing the availability of a new crash ping dashboard: > https://crash-pings.mozilla.org. > > Some of you may be familiar with Socorro <https://cras-stats.mozilla.org>, > our crash report dashboard. The difference is that crash pings are > default-on with telemetry, and don’t require user input to be sent (because > they do not contain PII: Personally identifiable information), whereas > reports require user input to be sent. We have far less volume of reports > than pings, and they are far more biased. This means that reports are not > the best source of data to, for example, determine top crashers: to get a > comprehensive view of stability, use ping data! > > This dashboard was adapted and reworked from the existing Telemetry-based > dashboard <https://mozilla.github.io/process-top-crashes/>. It uses Glean > crash ping data, which is now available for all platforms. This includes > Android crashes (native and Java), which we didn’t have in Telemetry! > > Our dashboard currently shows a sampling of the received pings in the past > week, where we limit results within groups of release channel and process > type. This ensures each channel and process type has some pings, but allows > us to reasonably process the total volume of data. We are working on > improving symbolication to be able to increase the sample size, however the > current sample size results in less than about 1.5% error in the 99% > confidence interval. > > The dashboard is still being developed and improved, but we are announcing > it now as it is moderately functional and may prove useful to you. If you > encounter any issues or have suggestions, please submit bugs on BMO under > the Crash Pings > :: Website > <https://bugzilla.mozilla.org/enter_bug.cgi?product=Crash%20Pings&component=Website> > component. > > We plan to move the existing automated topcrasher bug flagging to use this > crash ping data rather than the crash report data it currently uses. Note, > however, that this will never be a replacement for Socorro and crash > reports: crash ping data is a good place to start when triaging issues and > assessing stability, but the depth of information available from reports is > essential for debugging issues. > > Thanks all, > > Alex Franchuk > ​ > > -- > You received this message because you are subscribed to the Google Groups " > dev-platform@mozilla.org" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dev-platform+unsubscr...@mozilla.org. > To view this discussion visit > https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/24ac77b1-ef3a-4b30-9024-77e2ebcc6772%40mozilla.com > <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/24ac77b1-ef3a-4b30-9024-77e2ebcc6772%40mozilla.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "dev-platform@mozilla.org" group. To unsubscribe from this group and stop receiving emails from it, send an email to dev-platform+unsubscr...@mozilla.org. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CADa3RMO6joTJRc6XSZzrD2GXaiCZuSs%3DGYc593evOX51d%3DY50g%40mail.gmail.com.
