Crash reporting overhaul: Difference between revisions

Crash reporting overhaul (view source)

Revision as of 09:37, 11 August 2022

454 bytes added , 11 August 2022

→‎Rationale: added a bit more context about crash telemetry in Fenix

Dexterp37

43

edits

@@ Line 232: / Line 232: @@
 The [https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/crash-ping.html crash ping]
-uses legacy telemetry. This is problematic for a number of reasons: we don't
+uses legacy telemetry. This is problematic for a number of reasons: legacy telemetry is exclusively available in Firefox Desktop ('''not in GeckoView'''), we don't
-have good interfaces to process them, the tools we use to extract information
+have good interfaces to process these pings, the tools we use to extract information
-can be complicated to use and the legacy telemetry framework doesn't see active
+can be complicated and mobile products are using a more modern data collection system,
-development as it's been largely replaced by
+[https://docs.telemetry.mozilla.org/concepts/glean/glean.html Glean].
-[https://docs.telemetry.mozilla.org/concepts/glean/glean.html Glean]. Last but
-not least Fenix does not support legacy telemetry. While Fennec had
+Firefox for Android (aka Fenix) does not submit the crash ping that Firefox Desktop submits.
-full-featured crash pings Fenix doesn't have any at all, leading to a rather
+It instead records a [https://dictionary.telemetry.mozilla.org/apps/fenix/metrics/crash_metrics_crash_count crash_count metric] that's submitted in the metrics ping (via AC-'s [https://github.com/mozilla-mobile/android-components/tree/main/components/lib/crash lib-crash]). Fenix does collect crash-related information through Sentry. The old Firefox for Android (Fennec) had
+full-featured crash pings but Fenix doesn't have any at all, leading to a rather
 large blind spot in our telemetry.