This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Refactor Glean metrics abstraction to be less error prone #2706
Labels
E5
Estimation Point: about 5 days
eng:health
Improve code health
Feature:Telemetry
P1
Current sprint
Milestone
Comments
We should use |
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 15, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 19, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 19, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Aug 19, 2019
boek
pushed a commit
that referenced
this issue
Aug 19, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
E5
Estimation Point: about 5 days
eng:health
Improve code health
Feature:Telemetry
P1
Current sprint
Currently we are hardcoding strings that map Glean metrics from the
metrics.yaml
file to the extras passed in insidemetrics.kt
. This leads to crashes like #2688 as we have no safeguards to ensure that the metrics align. This is especially worrisome because, by default, telemetry events do not get send in dev builds, so an unsuspecting dev could believe they were testing properly and still ship a crash (which is what happened in my case 😅: #2705 )It would be great if we could implement a system that would automatically detects these misalignment (or at least test for them before being merged in). This will help us avoid many similar crashes in the future.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: