43
edits
Crash reporting overhaul: Difference between revisions
Jump to navigation
Jump to search
→Plan: made it clear that this won't be replacing legacy telemetry at first
(→Glean-based crash pings: added a link to lib-crash) |
(→Plan: made it clear that this won't be replacing legacy telemetry at first) |
||
| 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: | ||
* First of all the new Glean-based crash ping needs to be designed. Some parts of it might require | * First of all the new Glean-based crash ping needs to be designed. Some parts of it might require adding a new metric type to Glean's (e.g. stack traces) | ||
* Once this is done the code in the CrashManager that assembles the ping for child process crashes needs to be adjusted to use Glean | * Once this is done the code in the CrashManager that assembles the ping for child process crashes needs to be adjusted to use Glean in addition to legacy telemetry | ||
* The crash reporter client needs to be instructed to send Glean crash pings. Currently Glean doesn't support C++ so this work will need to happen after we rewrite the crash reporter client | * 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 | ||
* | * Support for the new crash ping needs to be added to Fenix | ||
* Eventually the crash-ping from legacy telemetry will need to be decommissioned | |||
== minidump-analyzer == | == minidump-analyzer == | ||