Closed
Bug 1330331
Opened 8 years ago
Closed 7 years ago
[tracker] runbooks and ack-able alerts and SLOs, oh my
Categories
(Taskcluster :: Operations and Service Requests, task)
Taskcluster
Operations and Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bstack, Assigned: bstack)
References
Details
Note: According to https://madamgrammar.com/2016/10/21/oh-my-could-we-stop-using-this-cliche/, this bug title is cliche. Oh well, I'm sticking to it.
We've decided to get serious about monitoring the health of Taskcluster. With that in mind, we're going to have to start discussing:
* gather new metrics about how tc is functioning
* adding alerting on metrics we're gathering
* figuring out what to do when those alerts fire
* figuring out how to communicate within ourselves and to the outside world during a fire.
* figuring out how to take bug reports from the outside world
* ????
* and more!
This will be a meta-bug to track our work on this. As I type this we're working on a retrospective for a slowdown we had last night and we'll update this bug with the results of our discussion.
Updated•8 years ago
|
Summary: runbooks and ack-able alerts and SLOs, oh my → [tracker] runbooks and ack-able alerts and SLOs, oh my
Updated•7 years ago
|
Blocks: tc-stability
Assignee | ||
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Updated•7 years ago
|
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Operations → Operations and Service Requests
You need to log in
before you can comment on or make changes to this bug.
Description
•