Closed Bug 778809 Opened 8 years ago Closed 6 years ago

Pick useful histogram ranges for simplemeasures

Categories

(Mozilla Metrics :: Frontend Reports, defect, P2)

x86_64
Windows 7
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Moved to JIRA

People

(Reporter: taras.mozilla, Unassigned)

References

Details

(Whiteboard: [Telemetry:P1][JIRA METRICS-1356])

histograms like startup_sessionrestoredreadbytes are created out of a single number per submission. We should be able to normalize the histogram parameters to get a useful normal distribution.
I meant simple_measures_startupsessionrestoredreadbytes. At the moment, the histogram is completely unusable.
Need telemetry team Px on that.
Target Milestone: Unreviewed → Backlogged - JIRA
Target Milestone: Backlogged - JIRA → Backlogged - BZ
This is important, but takes backseat to validation, etc
Priority: -- → P2
Whiteboard: [Telemetry:P2]
Duplicate of this bug: 727184
Whiteboard: [Telemetry:P2] → [Telemetry:P1]
Whiteboard: [Telemetry:P1] → [Telemetry:P1][JIRA METRICS-1356]
Target Milestone: Backlogged - BZ → Moved to JIRA
High priority:
startupsessionrestoredreadbytes, failedProfileLockCount, modifiedUnpacked, modifiedExceptInstallRDF, modifiedXPI, installedUnpacked,

Lower priority, but still important:
- firstPaint, sessionRestored, shutdownDuration
- AMI_startup_begin, AMI_startup_end, XPI_startup_begin, XPI_startup_end, XPI_bootstrap_addons_begin, XPI_bootstrap_addons_end
histograms have been retired at this point.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.