Closed
Bug 859969
Opened 13 years ago
Closed 13 years ago
add nagios monitor for firefox health report (origin)
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cturra, Assigned: cturra)
Details
now that fhr is in production and soon to be rolled out to the firefox release channel, we should get nagios monitoring in place.
this service is fronted with Akamai, which caches content from fhr-origin.cdn.mozilla.net. we're going to start with monitoring just -origin, since it's ultimately where the content comes from!
Comment 1•13 years ago
|
||
Specifically, create a nagios check to monitor https://fhr-origin.cdn.mozilla.net/en-US/. Should be 200 OK, with some content. Look for the string "Firefox Health Report".
| Assignee | ||
Comment 2•13 years ago
|
||
a new hostgroup was created for this service:
"firefox-health-report" => {
alias => "Firefox Health Report service"
},
...a new service group was created for this string check:
"http-string-firefox-healthreport" => {
service_description => "fhr-origin.cdn.mozilla.net - http string",
check_command => 'check_https_string!fhr-origin.cdn.mozilla.net!/en-US/!\'Firefox Health Report\'',
normal_check_interval => 5,
contact_groups => 'sysalerts',
hostgroups => $::fqdn ? {
"nagios1.private.phx1.mozilla.com" => [
"firefox-health-report",
],
default => [
]
}
},
and finally the host definition:
"fhr-origin.cdn.mozilla.net" => {
parents => "generic.zlb.phx.mozilla.net",
hostgroups => [
"https-websites",
"generic-cluster-websites",
"firefox-health-report",
]
},
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•7 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•