> This works great, thank you. My biggest concern now is when a > distributed server stops reporting such that a service > becomes stale, it's going to happen to a couple hundred > services and send out a correspondingly huge amount of email > notifications. Any thoughts on how to limit this?
Use service dependencies. Define a 'nagios running' service check for your distributed server checked every 1 min, and then make all of the passives depend on this service. Thus, if the distributed nagios goes belly-up then this 'nagios running' will go to critical or unknown, and then the service dependencies will prevent notification on all of the passive services (which will go stale AFTER the distributed nagios check, if you check that often enough). Steve ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
