Oh how the time gets away from you…
I have Nagios (Refer to the April 15th post) installed and in production. I am still tweaking the configuration and rolling out device monitoring.
Adding anything to be monitored is time consuming. Some might even think it is very time consuming. The three main files are switch.cfg, windows.cfg and printer.cfg and all editing is done through either vi or some other text editor. There are also other configurations and add-ons for monitoring Netware and/or Linux/Unix machines.
Windows server monitoring requires two main parts: installing the NSClient++ on the actual server and adding the necessary configuration to the windows.cfg on the Nagios box. For a clear how-to on installing the NSClient++ refer to this blog post. You may find that additional server config, such as loading WMI or other SNMP reporting may be required to collect the necessary data.
The windows.cfg editing is fairly straight forward. This PDF file on the Nagios website will be very helpful.
1) Add the host definition (insert your values for the bold text)
use windows-server ; Inherit default values from a Windows server template (make sure you keep this line!)
alias My Windows Server
2) Add the services or counters to be monitored
service_description NSClient++ Version
service_description CPU Load
check_command check_nt!CPULOAD!-l 5,80,90
service_description Memory Usage
check_command check_nt!MEMUSE!-w 80 -c 90
NOTE: Any time the Nagios cfg files are edited you MUST verify the config and then restart the nagios service. Failure to do this will not show the correct config in Nagios Service Detail or may cause a failure of the nagios service.
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
service nagios restart
Check this tool out and join the 3 million other users!