> In order for freshness checks to work in 2.0 and up, you have to set as > follows. > check_period 24x7 > passive_checks_enabled 1 > active_checks_enabled 0 ; these are all passive checks > check_freshness 1 > check_command check-freshness-stale!"Service report > not received within time period" > freshness_threshold 1800 ; Set your own number here > > (My "check-freshness-stale" returns 2, and send the arg as the string.) > > This is a change in 2.0 and up. In 1.x, A freshness check would be run even > of the service was outside the check period. In 2.x the freshness check will > only be run if the service is in its check period. > > This means you will get the annoying gif in the status.cgi. Such services > being critical will also not show up in the tac cgi as an unhanded problem, > but rather as a disabled problem. For GUI users, this can be very > misleading. I hacked the tac.cgi to have them show up as unhandled problems.
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? Would disabling notifications and just keeping tabs on the distributed server itself, perhaps with parent hosting or service dependence, be a better approach? I ask as it's my first Nagios implementation. Thanks. -- - Kyle --------------------------------------------- [EMAIL PROTECTED] http://www.panix.com/~kylet --------------------------------------------- ------------------------------------------------------- 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
