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)

defect

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)
Priority: -- → P2
Whiteboard: [unifiedTelemetry][rC]
Assignee: nobody → rmiller
See Also: → 1177737
We want to set up a separate email address for unified telemetry alerts (vs general pipeline alerts).
Iteration: --- → 43.1 - Aug 24
Rob will talk to whd and mreid and decide on what alerting we want for production.
Priority: P2 → P1
Blocks: 1210907
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.
Depends on: 1215597
Priority: P1 → P2
Covered by the generic docType monitor in prod.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.