Closed
Bug 1572775
Opened 6 years ago
Closed 6 years ago
Make it easy to discover which crons/handlers/etc need to be monitored and how
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bstack, Assigned: bstack)
References
Details
This will be used by cloudops to set up alerts.
Assignee | ||
Updated•6 years ago
|
Blocks: tc-cloudops
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → bstack
Status: NEW → ASSIGNED
Comment 1•6 years ago
|
||
Is this a dupe of bug 1561338?
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 2•6 years ago
|
||
whoops, didn't mean to close
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 3•6 years ago
|
||
Ah, it is a dupe of that. I'm going to change it to be about exposing this information to operators.
Summary: Make sure that crons and handlers log a recognizable message on every iteration → Make it easy to discover which crons/handlers/etc need to be monitored and how
Assignee | ||
Updated•6 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 4•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•