Closed
Bug 1277503
Opened 8 years ago
Closed 7 years ago
Remove child payload collection code in Telemetry
Categories
(Toolkit :: Telemetry, defect, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
DUPLICATE
of bug 1443600
Tracking | Status | |
---|---|---|
firefox49 | --- | affected |
People
(Reporter: gfritzsche, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [measurement:client])
With bug 1218576 fixed, we can remove the child payload collection code in TelemetrySession.jsm.
Reporter | ||
Comment 1•8 years ago
|
||
We also need to update about:telemetry to handle this properly (and to remove the child payload selector there).
Comment 2•7 years ago
|
||
There are five things recorded in childPayloads:
1. version (( which is 4, same as the other two places in the main ping that report version ))
2. simpleMeasurements (( process startup timings for this particular child process mostly ))
3. chromeHangs (( only valid if the profiler's built, enabled, on windows, and toolkit.telemetry.enabled AND if the hang is longer than 5s ))
4. log (( only user is Telemetry Experiments in the parent process (and going away, see bug 1415284) ))
5. webrtc (( Of a 1% sample of main pings from Jan 26, less than 0.01% of them had webrtc stats in the child payloads ))
From the point of view of preservation, it looks as though we probably don't need to bother?
Comment 3•7 years ago
|
||
We actually have a plan and timeline for this now!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•