canmove, Confirmed users
2,850
edits
ReleaseEngineering/How To/Process nagios alerts: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Process nagios alerts (view source)
Revision as of 08:04, 30 September 2015
, 30 September 2015no edit summary
(initial content) |
ChrisCooper (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Release Engineering How To|Process nagios alerts}} | {{Release Engineering How To|Process nagios alerts}} | ||
This page covers various nagios alerts, and gives pointers to how to resolve them. It also marks alerts that should now be automatically handled by the new automation infrastructure, so bugs can be filed as appropriate. | This page covers various nagios alerts, and gives pointers to how to resolve them. It also marks alerts that should now be automatically handled by the new automation infrastructure, so bugs can be filed as appropriate. | ||
= How to add/modify releng nagios alerts = | |||
The releng nagios alerts live in the [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=5734910 sysadmins svn repo]. | |||
svn co svn+ssh://svn.mozilla.org/sysadmins/puppet/trunk/modules/nagios/manifests/releng | |||
When adding new alerts, it's preferable to create hostgroups to define a class of machines that will share alerting characteristics, rather than adding alerts for single machines. | |||
= Processing existing alerts = | |||
{| cellpadding="10" cellspacing="0" border="1" | {| cellpadding="10" cellspacing="0" border="1" | ||