Closed Bug 1048576 Opened 10 years ago Closed 9 years ago

Centralized logging/monitoring for runner

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Unassigned)

Details

As we move more and more things to runner, we'll want to be able to distinguish occasionally task failures from actual outages. We'll also find ourselves wanting to know which hosts ran which task, when, or just how many 'hg clone' operations runner is running, or when the last time a certain host rebooted (as opposed to restarting buildbot). A good way to accomplish all of this may be to send status reports to relengapi, and then make them searchable and viewable there. That could be as simple as a list of all tasks and their success/failures, plus hostname.
Component: Other → Tools
QA Contact: pmoore → hwine
woooo bug 2^20 Guessing this is wontfix with BB->TC migration?
Flags: needinfo?(dustin)
yeah, we have good reporting from runner, and yeah, migration.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(dustin)
Resolution: --- → FIXED
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.