Closed
Bug 1162553
Opened 9 years ago
Closed 3 years ago
Monitor telemetry errors by appUpdateChannel and appBuildId
Categories
(Data Platform and Tools :: Monitoring & Alerting, defect, P2)
Data Platform and Tools
Monitoring & Alerting
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Assigned: rmiller)
References
Details
(Whiteboard: [unifiedTelemetry][rC])
We should monitor errors in the telemetry data stream by Channel and Build ID so that we can determine in which build a problem starts and in which build it gets fixed.
Updated•9 years ago
|
Priority: -- → P1
Reporter | ||
Updated•9 years ago
|
Assignee: nobody → kparlante
Reporter | ||
Updated•9 years ago
|
Priority: P1 → P2
Whiteboard: [unifiedTelemetry][rC]
Updated•9 years ago
|
Assignee: kparlante → rmiller
Comment 1•9 years ago
|
||
This is a good one to start with. Useful to look at: https://github.com/mozilla-services/data-pipeline/blob/master/heka/sandbox/modules/fx.lua https://github.com/mozilla-services/data-pipeline/blob/master/heka/sandbox/filters/firefox_plugin_hangs.lua
Updated•9 years ago
|
Iteration: --- → 43.1 - Aug 24
Comment 2•9 years ago
|
||
Rob will check in on this, polish anything up, and close out the bug.
Priority: P2 → P1
Updated•9 years ago
|
Priority: P1 → P2
Updated•7 years ago
|
Iteration: 43.1 - Aug 24 → ---
Component: Metrics: Pipeline → Monitoring & Alerting
Product: Cloud Services → Data Platform and Tools
Comment 3•3 years ago
|
||
Mission control was implemented. Closing unless this is more specific needs.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•