From Fedora Project Wiki

m (1 revision(s))
m (Fixed templates and links)
Line 16: Line 16:
= Initial Configuration =
= Initial Configuration =
== CGI Access ==
== CGI Access ==
To view information in nagios (anything with cgi-bin in the path) you need to be able to grant yourself access.  After checking out the Puppet CVS tree as described in the  [http://fedoraproject.org/wiki/Infrastructure/SOP/Puppet Puppet SOP]  you first need to edit configs/system/nagios/cgi.cfg and append your FAS username to 'authorized_for_system_commands'
To view information in nagios (anything with cgi-bin in the path) you need to be able to grant yourself access.  After checking out the Puppet CVS tree as described in the  [[Infrastructure/SOP/Puppet |Puppet SOP]]  you first need to edit configs/system/nagios/cgi.cfg and append your FAS username to 'authorized_for_system_commands'
== Contact Information ==
== Contact Information ==
{{Template:Warning}} You must configure a contacts file to be able to acknowledge [http://fedoraproject.org/wiki/Infrastructure/SOP/Outage outages]  
{{Message/warning2 | You must configure a contacts file to be able to acknowledge [[Infrastructure/SOP/Outage |outages]]}}
Create a new file named 'fasname.cfg' in configs/system/nagios/contacts/ with the following details:
Create a new file named 'fasname.cfg' in configs/system/nagios/contacts/ with the following details:
<pre>
<pre>
Line 33: Line 33:
}
}
</pre>
</pre>
{{Template:Caution}} Using the 24x7 notification period may cause duplicate messages if you are a member of sysadmin-main, in which case you can specify 'never' instead
{{Message/warning3 | Using the 24x7 notification period may cause duplicate messages if you are a member of sysadmin-main, in which case you can specify 'never' instead}}


Next append your name to the 'members' section of configs/system/nagios/contactgroups/fedora-sysadmin-email.cfg
Next append your name to the 'members' section of configs/system/nagios/contactgroups/fedora-sysadmin-email.cfg
Line 41: Line 41:


== Commit Changes ==
== Commit Changes ==
{{Template:Warning}} Remember to "cvs add" the contacts/fasname.cfg files
{{Message/warning2 | Remember to "cvs add" the contacts/fasname.cfg files}}


Commit changes by running cvs commit -m "Adding fasname to Nagios" and then mark the changes for distribution by make install
Commit changes by running cvs commit -m "Adding fasname to Nagios" and then mark the changes for distribution by make install
Line 61: Line 61:


A message stating "(1% inode=99%)" means that the diskspace is critical '''not''' the inode usage and is a sign that more diskspace is required.
A message stating "(1% inode=99%)" means that the diskspace is critical '''not''' the inode usage and is a sign that more diskspace is required.


= Further Reading =
= Further Reading =
* [http://fedoraproject.org/wiki/Infrastructure/SOP/Puppet Puppet SOP]  
* [[Infrastructure/SOP/Puppet |Puppet SOP]]  
* [http://fedoraproject.org/wiki/Infrastructure/SOP/Outage Outages SOP]
* [[Infrastructure/SOP/Outage |Outages SOP]]

Revision as of 13:59, 30 May 2008

Nagios: Standard Operating Procedure

Contact Information

Owner: Fedora Infrastructure Team

Contact: #fedora-admin, sysadmin-main & sysadmin-noc groups

Location: Anywhere

Servers: noc1, noc2, puppet1

Purpose: This SOP is to describe nagios configurations

Initial Configuration

CGI Access

To view information in nagios (anything with cgi-bin in the path) you need to be able to grant yourself access. After checking out the Puppet CVS tree as described in the Puppet SOP you first need to edit configs/system/nagios/cgi.cfg and append your FAS username to 'authorized_for_system_commands'

Contact Information

Stop (medium size).png
You must configure a contacts file to be able to acknowledge outages

Create a new file named 'fasname.cfg' in configs/system/nagios/contacts/ with the following details:

define contact{
contact_name            fasname
alias                   Real Name
service_notification_period   24x7
host_notification_period      24x7
service_notification_options  w,u,c,r
host_notification_options     d,u,r
service_notification_commands notify-by-email
host_notification_commands    host-notify-by-email
email                   Email address (any)
}
Warning.png
Using the 24x7 notification period may cause duplicate messages if you are a member of sysadmin-main, in which case you can specify 'never' instead

Next append your name to the 'members' section of configs/system/nagios/contactgroups/fedora-sysadmin-email.cfg

nagios-external

The same changes will need to be applied with the nagios-external configuration (configs/system/nogios-external)

Commit Changes

Stop (medium size).png
Remember to "cvs add" the contacts/fasname.cfg files

Commit changes by running cvs commit -m "Adding fasname to Nagios" and then mark the changes for distribution by make install

Understanding the Messages

General

Nagios notifications are generally easy to read, and follow this consistent format:

** PROBLEM/ACKNOWLEDGEMENT/RECOVERY alert - hostname/Check is WARNING/CRITICAL/OK **
** HOST DOWN/UP alert - hostname **

Reading the message will provide extra information on what is wrong.

Disk Space Warning/Critical

Disk space warnings normally include the following information:

DISK WARNING/CRITICAL/OK - free space: mountpoint freespace(MB) (freespace(%) inode=freeinodes(%)):

A message stating "(1% inode=99%)" means that the diskspace is critical not the inode usage and is a sign that more diskspace is required.

Further Reading