Closed
Bug 1620175
Opened 6 years ago
Closed 4 years ago
Get rid of Uptake Histogram Telemetry
Categories
(Firefox :: Remote Settings Client, enhancement, P3)
Firefox
Remote Settings Client
Tracking
()
RESOLVED
FIXED
100 Branch
| Tracking | Status | |
|---|---|---|
| firefox100 | --- | fixed |
People
(Reporter: leplatrem, Assigned: leplatrem)
References
Details
Attachments
(1 external file)
AFAIK Normandy and Remote Settings are the only components using uptake telemetry.
And now that Events Telemetry became our main source of metrics, I believe we can get rid of our categorical keyed histogram.
Comment 1•6 years ago
|
||
Events telemetry is sampled, whereas the histogram is more "complete". It feels like it might be worth having a check on histogram telemetry for unusual situations where the sampling can be misleading. (Maybe this is based on a misunderstanding of the statistics involved and it isn't worth worrying about such extreme cases.)
Can we articulate the cost of the histogram? It seems like it doesn't add a lot of computational expense, for example, although I'm not an expert in that. I guess it adds a little maintenance overhead? What else?
| Assignee | ||
Comment 2•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → mathieu
Status: NEW → ASSIGNED
| Assignee | ||
Updated•4 years ago
|
Group: mozilla-employee-confidential
Pushed by mleplatre@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d4998b388b53
Get rid of Telemetry histograms r=gbeckley
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•