Closed
Bug 1261400
Opened 8 years ago
Closed 4 years ago
cerberus should file bugs for expiring probes
Categories
(Data Platform and Tools :: Monitoring & Alerting, defect, P3)
Data Platform and Tools
Monitoring & Alerting
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rvitillo, Assigned: benwu)
References
Details
RyanVM: "I think what would be cool (albeit lower priority) would be auto-filing bugs on every merge day (in the right component) for Telemetry probes expiring on the next merge day. That'll gives teams 6 weeks of notice to figure out what they want to do an act accordingly."
Updated•8 years ago
|
Points: --- → 2
Priority: -- → P3
Comment 1•8 years ago
|
||
The context of that email being that I end up filing bug every 6 weeks along the lines of "XXX test is going to permafail when the Gecko version number is bumped to YY" and 99% of the time it's due to Telemetry probes expiring and tests not being happy about it. Seems like we shouldn't need Try simulation pushes to uncover that.
Comment 2•8 years ago
|
||
(In reply to Chris H-C :chutten from comment #2) > "In the right component?" Hey, I never said that cool meant practical!
Comment 3•8 years ago
|
||
"In the right component?"
Updated•7 years ago
|
Component: Metrics: Pipeline → Monitoring & Alerting
Product: Cloud Services → Data Platform and Tools
Comment 4•4 years ago
|
||
Cerberus is dead! Long live probe_expiry_alert!
Assignee | ||
Comment 5•4 years ago
|
||
Closing along with bug 1610616
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•