Confirmed users
417
edits
Crash reporting overhaul: Difference between revisions
Jump to navigation
Jump to search
Change the Glean-based ping plan to go with a more incremental approach
(→Plan: made it clear that this won't be replacing legacy telemetry at first) |
(Change the Glean-based ping plan to go with a more incremental approach) |
||
| Line 249: | Line 249: | ||
This migration requires several steps with changes happening in different parts | This migration requires several steps with changes happening in different parts | ||
of the codebase: | of the codebase: | ||
* | * Prepare the design of a minimal crash ping that can be implemented using existing client- and server-side machinery. | ||
* | * Add support for this minimal Glean-based crash ping to Firefox desktop (inside the CrashManager) and Fenix where it needs to be done from scratch. | ||
* | * Once the new ping's functionality has been validated, broaden the design to include parts that might require adding a new metric type (such as stack traces) and include all of the legacy crash ping information. | ||
* | * Modify the code previously introduced to fully populate the Glean-based ping and make its payload match the legacy one. This might need extra work on the Fenix side, especially to capture stack traces. | ||
* Last but not least the crash reporter client needs to be instructed to send Glean crash pings in addition to legacy telemetry pings. Currently Glean doesn't support C++ so this work will need to happen after we rewrite the crash reporter client. | |||
* Decommission the legacy telemetry crash ping and remove the relevant code from Firefox desktop. | |||
== minidump-analyzer == | == minidump-analyzer == | ||