Closed Bug 745000 Opened 13 years ago Closed 13 years ago

nagios check on sumo/services/monitor

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jsocol, Assigned: afernandez)

References

Details

SUMO has a page specifically designed to monitor system health in both a human and machine readable way: https://support.mozilla.org/services/monitor Nagios should do an http status check on that page and report into #sumodev when it returns anything other than a 200 OK. The page is currently broken--it has been for a while--and nagios never noticed. We're fixing in bug 744997.
Depends on: 744997
I put bug 744997 as a blocker on this, but we can and should turn on monitoring as soon as we can, regardless of the state of 744997.
Assignee: server-ops → afernandez
The alert has been added and confirm it shows on #sumodev 12:21 < nagios-phx1> [159] sumo.zlb.phx.mozilla.net:support.mozilla.org - https - /services/monitor is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 INTERNAL SERVER ERROR - 14954 bytes in 0.863 second response time
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.