Closed
Bug 733467
Opened 12 years ago
Closed 9 years ago
Telemetry frontend: give a sense for how many actual users a data point/chart represents
Categories
(Mozilla Metrics :: Frontend Reports, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Backlogged - BZ
People
(Reporter: cww, Unassigned)
Details
A number of the telemetry measures are lots of submissions (for example cycle collector is actually thousands of data points per telemetry ping). Therefore, it can be hard sometimes to tell that a histogram that adds up to over 20K is actually only 5 telemetry ping. We should make it clear how many actual users each histogram or data point represents. Also a user submitting 20K data points can drown out a user submitting only a thousand. One way would be to have each ping = 1 datum and do a histogram of medians/means/etc. Another may be to rescale each user's graph to a normalized single total value (like 1000). The metrics team may have more clever ideas, also.
Updated•12 years ago
|
Group: metrics-private
Updated•12 years ago
|
Whiteboard: [Telemetry]
Comment 1•12 years ago
|
||
Marking: in group of > 33 asks for Telemetry that need PM priority before triage/scheduling.
Status: NEW → ASSIGNED
Whiteboard: [Telemetry] → Telemetry -- needs PM project priority
Updated•11 years ago
|
Whiteboard: Telemetry -- needs PM project priority → [Telemetry] -- needs PM project priority
Comment 3•9 years ago
|
||
This is being fixed with the new telemetry data and pipeline.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Whiteboard: [Telemetry] -- needs PM project priority
You need to log in
before you can comment on or make changes to this bug.
Description
•