Closed
Bug 1216191
Opened 9 years ago
Closed 7 years ago
[meta] Properly document the Telemetry ping data
Categories
(Toolkit :: Telemetry, defect, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox44 | --- | affected |
People
(Reporter: gfritzsche, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [measurement:client] [measurement:client:project])
We started documenting the Telemetry session payload in main-ping.rst, but haven't completely documented the individual fields. We should at least go through the top-level fields and document their intent and contents. We also need to document properly when which field is set and clearly show whether fields are in the "base" or "extended" data set.
Reporter | ||
Updated•9 years ago
|
Keywords: meta
Whiteboard: [unifiedTelemetry] [measurement:client] → [measurement:client] [measurement:client:tracking]
Reporter | ||
Updated•9 years ago
|
Summary: Properly document the Telemetry session payload → [meta] Properly document the Telemetry session payload
Reporter | ||
Updated•8 years ago
|
Whiteboard: [measurement:client] [measurement:client:tracking] → [measurement:client]
Reporter | ||
Updated•8 years ago
|
Priority: P3 → P2
Reporter | ||
Updated•8 years ago
|
Priority: P2 → P3
Summary: [meta] Properly document the Telemetry session payload → [meta] Properly document the Telemetry ping data
Whiteboard: [measurement:client] → [measurement:client] [measurement:client:project]
Reporter | ||
Comment 1•7 years ago
|
||
I moved the remaining dependencies to bug 1292530, closing this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•