Closed Bug 1226959 Opened 9 years ago Closed 9 years ago

Make builds-4hr Nagios alerts harder to overlook

Categories

(Infrastructure & Operations :: Infrastructure: Other, task)

Product:
Infrastructure & Operations
Component:
Infrastructure: Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: emorley, Unassigned)

References

Details

Please can the nagios checks added in bug 912463 for builds 4hr also be sent to 
release-engineering@lists.mozilla.org , since at the moment it's only being emailed to sheriffs@ and so the people seeing those aren't the ones who can fix it.

ie:
builddata.pub.build.mozilla.org/http file age - /buildjson/builds-*

Many thanks :-)
The alerts already go to #buildduty where the releng buildduty people look for issues (nagios alerts are not mailed to mailing lists). release-engineering is a public list and isn't the appropriate audience.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Yeah I realise they already go there - but they've been ignored until now.
Is there an internal-only mailing list (release@m.c ?) we can send them to instead in the meantime?

If you wish to close this, it's WONTFIX rather than WORKSFORME.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Add release-engineering mailing list to builds-4hr Nagios alerts recipients → Make builds-4hr Nagios alerts harder to overlook
The options from our end are email or irc. Give us a destination and we'll send them there but I'm unclear that we can help with making either of those harder to overlook.
Depends on: 1227145
:emorley adding email alerts won't actually address the problem, since those are ignored more than #buildduty alerts. I've brought up your concern that the alerts are not being dealt with properly, though, and we've opened bug 1227145 to deal with that.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → WONTFIX
Bug 1227145 sounds good, thank you :-)
You need to log in before you can comment on or make changes to this bug.