Closed
Bug 823178
Opened 13 years ago
Closed 13 years ago
Disable notifications for nagios alerts on panda checks.
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: ashish)
Details
So, we saw many of the panda's in pods and otherwise alerting on PING checks.
A good many of these fail for not having a b2g uboot image up, others fail for needing any image or during normal android reboots, etc.
Per discussion with :dustin and after attempting to manually downtime them for many weeks (of which some downtimes didn't seem to stick) we should just disable notifications until we get the tie-in to mozpool way for monitoring.
Comment 1•13 years ago
|
||
Server ops folks, can you help out with this? For the moment, I'd like to remove notifications for the PING checks, since they're spamming #buildduty. I'm not sure how to do that.
Longer term (bug 815765) we may get rid of them, stub them out, or do something else with them.
Assignee: server-ops-releng → server-ops
Component: Server Operations: RelEng → Server Operations
QA Contact: arich → shyam
| Assignee | ||
Comment 2•13 years ago
|
||
Done :)
Assignee: server-ops → ashish
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 3•13 years ago
|
||
17:57:24 < dustin> | so, yeah, my thinking is that the host check should be check_dummy, with a service using check_mozpool
17:57:34 < dustin> | but we could just as well have the host check use check_mozpool, right?
17:57:45 < dustin> | dunno if that'd be easier, or more confusing, or what
17:58:54 < ashish> yes we could. in fact that doesn't even need tweaking the templates IIRC
17:59:09 < dustin> | even better
17:59:47 < ashish> yep, confirmed. check_command can be overwritten in the hosts manifest
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•13 years ago
|
||
This should probably stay closed in favor of bug 815765. The service group is downtimed until Jan 22, so they won't be notifying for now.
| Assignee | ||
Comment 5•13 years ago
|
||
Resolving in favour of Bug 815765, which has further discussion.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•