Host Checking

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of John McGowan
> Sent: Wednesday, April 27, 2005 10:54 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Host Checking
> 
> Found the FAQ item on this...  But I would still like and explanation
on
> how host checking kicks in when a problem with a service is detected. 

When a service on a host returns a non-OK state, the host is checked
using the host's check_command serially up to max_check_attempts. This
means that Nagios will stop all other checks and processing until
max_check_attempts for that host is reached. When questionable, a host
state must be definitively known as other hosts could be dependent on
the state of this host, to determine network reach-ability as it applies
to parenting, and to determine what alerts need to be triggered.
Generally you want your defined host check to be simple and finish as
quickly as possible.

If the host is found to be down, a host alert is triggered and service
alerts are suppressed unless this host was the child of another host
that is also down. If the parent is down, no alerts for this host are
sent out.

If the host is found to be up, a service alert alone is triggered.

I think that's it in a nutshell.

--
Marc


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id5hix
_______________________________________________
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