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.
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
Target Milestone: Unreviewed → Backlogged - BZ
Whiteboard: Telemetry -- needs PM project priority → [Telemetry] -- needs PM project priority
This is being fixed with the new telemetry data and pipeline.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 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.