Closed Bug 897371 Opened 11 years ago Closed 7 years ago

Investigate recreating/improving monitoring of our productdelivery cluster's upload artifacts.

Categories

(Release Engineering :: General, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: Callek, Unassigned)

References

Details

So a tidbit that came out of our conversation around "what still lives on CVS" reminded me all about the nagios checks we used to have on surf, before we improved and moved our productdelivery cluster. The checks primarily related to ensuring Nightlies existed, including l10n, across different branches, and were all up to date enough. http://bonsai.mozilla.org/rview.cgi?dir=mozilla/tools/tinderbox-configs/monitoring&cvsroot=/cvsroot&module=default This had its drawbacks, especially once we started watching for green builds, and new builds within the last day on our branches, which then broke our assumptions of "a new build every 24 hours". These checks also existed before we had sheriffs and when we had no QA people watching nightly resources, so it is entirely possible there is no need for us to check it with nagios anymore. That said, John wanted a bug on file so we can plan to revisit this when we get other pending nagios work under control and figure out if/how/whatever we want to pull this back into our monitoring plans.
Product: mozilla.org → Release Engineering
Where do the current suite of nagios alerts we rely on live?
Component: Other → Tools
QA Contact: hwine
Component: Tools → General
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.