Suppressing service notifications if host fails

[Mott Leroy]

Hi Marc -

Thanks for the quick response. Our check_command *seems* to be properly 
configured. it uses a check-host-alive plugin, and it DID return a 
CRITICAL state, but looking more closely at the logs, it seems like it 
wasn't reported as critical until some 4 hours or so after all the 
services reported themselves as CRITICAL. Don't individual services 
check on the health of their host? Why wouldn't it report the host as 
down until so much later?

All our hosts are defined as:

         check_command                   check-host-alive
         max_check_attempts              10
         notification_interval           120
         notification_period             24x7
         notification_options            d,u,r

Where check-host-alive is:

define command{
         command_name    check-host-alive
         command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 
5000,100% -c 5000,100% -p 1
         }

Thanks for any insight -

Mott


Marc Powell wrote:

>>
>>Nagios will automagically suppress service notifications for down
> 
> hosts
> 
>>if you have a properly configured host check_command that returns
>>CRICITAL or UNREACHABLE when the host is down.
> 
> 
> [edit] of course there is no UNREACHABLE status result from a plugin.
> That's determined internally by Nagios based on the 'parents' directive
> for each host. [/edit]
> 
> Sorry about that slight mis-information.
> 
> --
> Marc


-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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