Nagios - Revision history

Sstrutt: Reverted edits by Ipodsoft (talk) to last revision by Sstrutt

2013-10-03T14:54:29Z

Reverted edits by Ipodsoft (talk) to last revision by Sstrutt

Show changes

Ipodsoft at 04:10, 11 September 2013

2013-09-11T04:10:30Z

Show changes

Sstrutt: /* NRPE */ Minor rewording / formatting

2012-09-12T09:00:24Z

NRPE: Minor rewording / formatting

← Older revision		Revision as of 09:00, 12 September 2012
Line 329:		Line 329:

	== NRPE ==		== NRPE ==
	The Nagios Remote Plugin Executor allows Nagios checks to completed on remote servers in a similar fashion to performing checks on the Nagios server. Whilst its not always necessary, as many remote checks can be performed by probing remotely accessible services such as SNMP or HTTP, there are times when such checks are not suitable, for example...		The '''Nagios Remote Plugin Executor''' allows Nagios checks to completed on remote servers in a similar fashion to performing checks on the Nagios server. Whilst its not always necessary, as many remote checks can be performed by probing remotely accessible services (such as SNMP or HTTP), there are times when such checks are not suitable, for example...
	* Running checks that aren't easily achievable via SNMP		* Running checks that aren't easily achievable via SNMP
	* Checking services such as MySQL that ~~should only be~~ accessible ~~local to~~ the server		* Checking local services such as MySQL that aren't accessible remotely from the server
	* Running HTTP checks to test your web servers from more than one location		* Running HTTP checks to test your web servers from more than one location
	** EG local to server to ensure the web-server itself is OK, and remotely to check that access is likely to OK for global users		** EG local to server to ensure the web-server itself is OK, and remotely to check that access is likely to OK for global users

	The NRPE server that runs on remote monitored machines does require quite a few additional packages to be installed (see below for in-exhaustive list), and if you are concerned you try the alternative approach of getting data back from your remote server via SNMP as described in this example [[#Ubuntu_Software_Updates_Monitor\|Ubuntu Software Updates Monitor]]. This can make for a more lightweight solution, but will require you to write your own monitoring scripts to be called by the SNMP daemon. ~~Swings and roundabouts~~.		The NRPE server that runs on remote monitored machines does require quite a few additional packages to be installed (see below for in-exhaustive list), and if you are concerned you can try the alternative approach of getting data back from your remote server via SNMP as described in this example [[#Ubuntu_Software_Updates_Monitor\|Ubuntu Software Updates Monitor]]. This can make for a more lightweight solution, but will require you to write your own monitoring scripts to be called by the SNMP daemon.

			Additional packages required by NRPE...
	* mysql-common		* mysql-common
	* radiusclient1		* radiusclient1
Line 342:		Line 344:
	* snmp		* snmp

			=== Setup ===
	The procedures below will get NRPE running to monitor disk space, load and MySQL service availability on a remote server.		The procedures below will get NRPE running to monitor disk space, load and MySQL service availability on a remote server.

Sstrutt: /* Create SNMP Checks */ Added standard disk status check

2012-09-06T10:03:59Z

Create SNMP Checks: Added standard disk status check

← Older revision		Revision as of 10:03, 6 September 2012
Line 46:		Line 46:
	\|-		\|-
	\| <code> .1.3.6.1.4.1.24681.1.2.17.1.5.1 </code> \|\| System Volume 1 Space \|\| <code> 1.74 TB </code>		\| <code> .1.3.6.1.4.1.24681.1.2.17.1.5.1 </code> \|\| System Volume 1 Space \|\| <code> 1.74 TB </code>
			\|-
			\| <code> .1.3.6.1.4.1.24681.1.2.11.1.4.1 </code> \|\| Physical Disk 1 Status \|\| <code> ready </code>
	\|-		\|-
	\| <code> .1.3.6.1.4.1.24681.1.2.11.1.7.1 </code> \|\| Physical Disk 1 SMART Status \|\| <code> GOOD </code>		\| <code> .1.3.6.1.4.1.24681.1.2.11.1.7.1 </code> \|\| Physical Disk 1 SMART Status \|\| <code> GOOD </code>
Line 58:		Line 60:
	I created a new file, called <code>/etc/nagios3/conf.d/commands_qnap.cfg</code> and added the following...		I created a new file, called <code>/etc/nagios3/conf.d/commands_qnap.cfg</code> and added the following...

			==== System Temperature ====
	define command{		define command{
	command_name check_qnap_sys_temp		command_name check_qnap_sys_temp
Line 70:		Line 73:
	* <code> -u C </code> - The units of the metric being checked (appears in the check's Status Information column in Nagios display)		* <code> -u C </code> - The units of the metric being checked (appears in the check's Status Information column in Nagios display)

			==== Volume Status ====
	define command{		define command{
	command_name check_qnap_sysvol_status		command_name check_qnap_sysvol_status
Line 79:		Line 82:
	* <code> -r "Ready" </code> - The text expected back from the poll, anything else causes a critical error		* <code> -r "Ready" </code> - The text expected back from the poll, anything else causes a critical error

			==== Volume Space ====
	define command{		define command{
	command_name check_qnap_sysvol_space		command_name check_qnap_sysvol_space
Line 89:		Line 92:
	** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemVolumeTable.SysVolumeEntry.SysVolumeFreeSize.$ARG1$</code>		** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemVolumeTable.SysVolumeEntry.SysVolumeFreeSize.$ARG1$</code>

			==== Disk Status ====
			define command{
			command_name check_qnap_disk_status
			command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.11.1.4.$ARG1$ -m /etc/nagios3/mibs/QNAP-NAS.mib -l "Disk Status" -r 0
			}
			* <code> -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ </code> - The SNMP OID being checked, similar to above $ARG1$ is used as a command parameter so that I can create separate checks for the individual disks without creating a separate check command for each.
			** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemHdTable.HdEntry.HdStatus.$ARG1$</code>
			* <code> -m /etc/nagios3/mibs/QNAP-NAS.mib </code> - Path to the QNAP MIB file. The value returned is an integer, 0 for ready/good, a negative value for a fault. In order to translate the value (eg <code>-9</code>) to its actual meaning (eg <code>rwError</code>), Nagios needs access to the MIB file. You will need to download it from your NAS (from the Network Services \| SNMP Settings page), and copy it to path indicated on your Nagios server.
			* <code> -r 0 </code> - The data expected back from the poll, 0 maps to <code>ready</code>anything else causes a critical error

			==== Disk SMART Status ====
	define command{		define command{
	command_name ~~check_qnap_disk_status~~		command_name check_qnap_disk_smart_status
	command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ -l "SMART Info State" -r "GOOD"		command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ -l "SMART Info State" -r "GOOD"
	}		}
Line 98:		Line 111:
	* <code> -r "GOOD" </code> - The text expected back from the poll, anything else causes a critical error		* <code> -r "GOOD" </code> - The text expected back from the poll, anything else causes a critical error

			==== Disk Temperature ====
	define command{		define command{
	command_name check_qnap_disk_temp		command_name check_qnap_disk_temp
Line 104:		Line 118:
	* <code> -o .1.3.6.1.4.1.24681.1.2.11.1.3.$ARG1$ </code> - The SNMP OID being checked, as above $ARG1$ is used as a command parameter so that I can create separate checks for the individual disks without creating a separate check command for each.		* <code> -o .1.3.6.1.4.1.24681.1.2.11.1.3.$ARG1$ </code> - The SNMP OID being checked, as above $ARG1$ is used as a command parameter so that I can create separate checks for the individual disks without creating a separate check command for each.
	** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemHdTable.HdEntry.HdTemperature.$ARG1$</code>		** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemHdTable.HdEntry.HdTemperature.$ARG1$</code>


	=== Create Services ===		=== Create Services ===
Line 144:		Line 157:
	service_description Status Disk 1		service_description Status Disk 1
	check_command check_qnap_disk_status!1		check_command check_qnap_disk_status!1
			}

			define service{
			use generic-service
			hostgroup_name qnap-nas
			service_description SMART Disk 1
			check_command check_qnap_disk_smart_status!1
	}		}

Sstrutt: Added "Check Tuning" and Meta

2012-08-30T08:31:36Z

Added "Check Tuning" and Meta

@@ Line 16: / Line 16: @@
 ! Path   !! Description
 |-
-| <code> /etc/nagios3/conf.d </code>  || Config files
+| <code> /etc/nagios3/conf.d </code>  || Config files - anything in here is parsed as config, filenames are for your convenience and are irrelevant to Nagios
 |-
 | <code> /etc/nagios-plugins/config </code>  || Plugin commands
@@ Line 26: / Line 26: @@
 | <code> service nagios3 restart </code>  || Restart service (reloads config - will fail if config is invalid!)
 |}
 == Create SNMP Checks ==
@@ Line 171: / Line 170: @@
          alias                   NAS
          address                 192.168.1.200
+         }

Sstrutt: /* Introduction */ Reworded

2012-07-31T14:19:22Z

Introduction: Reworded

← Older revision		Revision as of 14:19, 31 July 2012
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	Nagios is an open source monitoring tool. Its standard (Core) version is free for download and use with no real limitations, its premium (XI) version offers additional features, most notably a GUI interface with which to configure it. Configuring Nagios ~~is a bit of head scratcher~~ at first, ~~you seem~~ to ~~have to make lots of~~ config ~~changes in different places~~ to get ~~things~~ working~~. But~~ once you've got the ~~concepts in your head, its relatively straight forward~~.		Nagios is an open source monitoring tool. Its standard (Core) version is free for download and use with no real limitations, its premium (XI) version offers additional features, most notably a GUI interface with which to configure it. Configuring Nagios can be challenging at first, requiring edits to multiple config files to get new monitoring working, but once you're got the logic and the pattern understood it becomes quite flexible.

	Nagios is centred around device polling (it can receive SNMP traps, but its a more advanced feature), and the presentation of state data. Though the first thing to appreciate is that Nagios doesn't actually do any monitoring, at its core it's a task scheduling and state management engine. It needs third party '''plugins''', which do the actual monitoring a report back the state of the host you're monitoring to it. There are plugins provided out-of-the-box, which will probably achieve most (if not all) of what you want.		Nagios is centred around device polling (it can receive SNMP traps, but its a more advanced feature), and the presentation of state data. Though the first thing to appreciate is that Nagios doesn't actually do any monitoring, at its core it's a task scheduling and state management engine. It needs third party '''plugins''', which do the actual monitoring a report back the state of the host you're monitoring to it. There are plugins provided out-of-the-box, which will probably achieve most (if not all) of what you want.

	~~This introduction is intended to explain the basic terminology, and get you going by demonstrating how to get a device or two monitored.~~

	== Terminology ==		== Terminology ==

Sstrutt: Added Applications category

2012-06-25T07:36:40Z

Added Applications category

← Older revision		Revision as of 07:36, 25 June 2012
Line 414:		Line 414:
	[[Category:SNMP]]		[[Category:SNMP]]
	[[Category:QNAP]]		[[Category:QNAP]]
			[[Category:Applications]]

Sstrutt: Added Monitoring category

2012-04-16T10:15:50Z

Added Monitoring category

← Older revision		Revision as of 10:15, 16 April 2012
Line 409:		Line 409:


			[[Category:Monitoring]]
	[[Category:Nagios]]		[[Category:Nagios]]
	[[Category:Ubuntu]]		[[Category:Ubuntu]]
	[[Category:SNMP]]		[[Category:SNMP]]
	[[Category:QNAP]]		[[Category:QNAP]]

Sstrutt: Added "Web Site Content and Response Time Monitoring"

2012-03-19T10:42:29Z

Added "Web Site Content and Response Time Monitoring"

@@ Line 336: / Line 336: @@
          notification_interval           0 ; set > 0 if you want to be renotified
+  }
 [[Category:Nagios]]

Sstrutt: /* Create SNMP Checks */ Updated checks that return text

2012-03-02T07:51:58Z

Create SNMP Checks: Updated checks that return text

← Older revision		Revision as of 07:51, 2 March 2012
Line 34:		Line 34:

	=== Define OID's to Poll ===		=== Define OID's to Poll ===
	Before you start you need to know what SNMP OID's you want to poll, and what ~~they're~~ values should be. For common devices and metrics you can often get by with a Google search or two, but it doesn't take much for you to need to get a bit more involved.		Before you start you need to know what SNMP OID's you want to poll, and what their values should be. For common devices and metrics you can often get by with a Google search or two, but it doesn't take much for you to need to get a bit more involved.

	When it comes to investigating what OID's you can poll for a specific device your friend is [http://www.wtcs.org/snmp4tpc/getif.htm GetIf].		When it comes to investigating what OID's you can poll for a specific device, your friend is [http://www.wtcs.org/snmp4tpc/getif.htm GetIf].

	Having downloaded the MIB and done some probing GetIf, I've decided I need to monitor the following OID's...		Having downloaded the MIB and done some probing GetIf, I've decided I need to monitor the following OID's...
Line 66:		Line 66:
	}		}
	* <code> -H '$HOSTADDRESS$' </code> - This is a standard wildcard for all check commands, Nagios substitutes the device's IP address		* <code> -H '$HOSTADDRESS$' </code> - This is a standard wildcard for all check commands, Nagios substitutes the device's IP address
	* <code> -o .1.3.6.1.4.1.24681.1.2.6.0 </code> - The SNMP OID being checked ** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemTemperature.0</code>		* <code> -o .1.3.6.1.4.1.24681.1.2.6.0 </code> - The SNMP OID being checked
			** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemTemperature.0</code>
	* <code> -w 45 </code> - The warning threshold		* <code> -w 45 </code> - The warning threshold
	* <code> -c 55 </code> - The critical threshold		* <code> -c 55 </code> - The critical threshold
Line 75:		Line 76:
	define command{		define command{
	command_name check_qnap_sysvol_status		command_name check_qnap_sysvol_status
	command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.17.1.6.$ARG1$ -l "Volume Status"		command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.17.1.6.$ARG1$ -l "Volume Status" -r "Ready"
	}		}
	* <code> -o .1.3.6.1.4.1.24681.1.2.17.1.6.$ARG1$ </code> - The SNMP OID being checked, $ARG1$ is used as a wildcard so that if I had more than one volume I could repeat the check for volume 1, 2 etc without creating a separate check command for each.		* <code> -o .1.3.6.1.4.1.24681.1.2.17.1.6.$ARG1$ </code> - The SNMP OID being checked, $ARG1$ is used as a wildcard so that if I had more than one volume I could repeat the check for volume 1, 2 etc without creating a separate check command for each.
	** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemVolumeTable.SysVolumeEntry.SysVolumeStatus.$ARG1$</code>		** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemVolumeTable.SysVolumeEntry.SysVolumeStatus.$ARG1$</code>
			* <code> -r "Ready" </code> - The text expected back from the poll, anything else causes a critical error


	define command{		define command{
	command_name check_qnap_sysvol_space		command_name check_qnap_sysvol_space
	command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.17.1.5.$ARG1$ -w $ARG2$: -c $ARG3$: -l "Volume Space" -u TB		command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.17.1.5.$ARG1$ -w $ARG2$: -c $ARG3$: -l "Volume Space" -u GB
	}		}
	* <code> -o .1.3.6.1.4.1.24681.1.2.17.1.5.$ARG1$ </code> - The SNMP OID being checked, as above $ARG1$ is used as a command parameter so that if I had more than one volume I could repeat the check for volume 1, 2 etc without creating a separate check command for each.		* <code> -o .1.3.6.1.4.1.24681.1.2.17.1.5.$ARG1$ </code> - The SNMP OID being checked, as above $ARG1$ is used as a command parameter so that if I had more than one volume I could repeat the check for volume 1, 2 etc without creating a separate check command for each.
Line 93:		Line 95:
	define command{		define command{
	command_name check_qnap_disk_status		command_name check_qnap_disk_status
	command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ -l "SMART Info State"		command_line /usr/lib/nagios/plugins/check_snmp -H '$HOSTADDRESS$' -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ -l "SMART Info State" -r "GOOD"
	}		}
	* <code> -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ </code> - The SNMP OID being checked, similar to above $ARG1$ is used as a command parameter so that I can create separate checks for the individual disks without creating a separate check command for each.		* <code> -o .1.3.6.1.4.1.24681.1.2.11.1.7.$ARG1$ </code> - The SNMP OID being checked, similar to above $ARG1$ is used as a command parameter so that I can create separate checks for the individual disks without creating a separate check command for each.
	** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemHdTable.HdEntry.HdSmartInfo.$ARG1$</code>		** <code>.iso.org.dod.internet.private.enterprises.storage.storageSystem.SystemInfo.SystemHdTable.HdEntry.HdSmartInfo.$ARG1$</code>
			* <code> -r "GOOD" </code> - The text expected back from the poll, anything else causes a critical error

	define command{		define command{