Closed
Bug 833858
Opened 12 years ago
Closed 6 years ago
send a distinct type for enumerated/categorical histograms in telemetry pings
Categories
(Toolkit :: Telemetry, defect, P4)
Toolkit
Telemetry
Tracking
()
RESOLVED
INVALID
People
(Reporter: froydnj, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [Telemetry:P2])
+++ This bug was initially created as a clone of Bug #811552 +++
- In the JSON (http://mxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/Histograms.json), certain histograms are of type "enumerated", meaning that they are categorical variables, whose outcomes represent distinct states, but whose ordering is usually not meaningful. At the moment, these are recorded as LinearHistograms, with buckets arranged approriately. I think it would make more sense to create a new histogram type for these, say CategoricalHistogram.
They are not "linear", in the sense that the values are precisely integer values, not discretized continuous measurements, so they have a different interpretation. Also, bucket "0" is a proper state and does not correspond to "underflow". Because of this, in our analysis we separate these variables anyway (using the rule histogram_type=="linear" && bucket_count==range[2]+1) and handle them differently. I think it would be more robust to record these inherently as a separate type, following the schema in the JSON.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [Telemetry:P2]
Reporter | ||
Updated•12 years ago
|
Summary: improvements for telemetry → send a distinct type for enumerated/categorical histograms in telemetry pings
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Comment 2•6 years ago
|
||
Bug 811552 tracks multiple issues, this one tracks one specific issue.
Let's keep it open to have separate concrete issues.
Comment 3•6 years ago
|
||
With the Probe Info Service telling us rich type information about our probes we don't need this any more.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•