Closed
Bug 1171630
Opened 9 years ago
Closed 7 years ago
Alerting for Unified Telemetry data quality
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kparlante, Assigned: rmiller)
References
Details
(Whiteboard: [unifiedTelemetry][rC])
Including but not limited to: - decoder errors json, gzip, size, schema (rate vs total by channel) - by channel and other dimensions (compare week to week)
Updated•9 years ago
|
Priority: -- → P2
Updated•9 years ago
|
Whiteboard: [unifiedTelemetry][rC]
Reporter | ||
Updated•9 years ago
|
Assignee: nobody → rmiller
Reporter | ||
Comment 1•9 years ago
|
||
We want to set up a separate email address for unified telemetry alerts (vs general pipeline alerts).
Updated•9 years ago
|
Iteration: --- → 43.1 - Aug 24
Reporter | ||
Comment 2•9 years ago
|
||
Rob will talk to whd and mreid and decide on what alerting we want for production.
Priority: P2 → P1
Assignee | ||
Comment 3•9 years ago
|
||
Came to agreement w/ kparlante, whd, and trink that this bug will cover alerting when we see a spike in the total number of errors of a particular type in a particular channel. Also opened bug 1210907, to cover a future refinement where we also track by build, so we know when a new build introduces a spike in a particular error type relative to the previous build.
Reporter | ||
Updated•9 years ago
|
Priority: P1 → P2
Comment 4•7 years ago
|
||
Covered by the generic docType monitor in prod.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•