> -----Original Message----- > From: Eric Frazier [mailto:[EMAIL PROTECTED] > Sent: Monday, September 24, 2007 12:29 PM > To: Marc Powell > Cc: [email protected] > Subject: Re: [Nagios-users] Suppressing notifications due to Unreachable > state due to parent config > > Marc Powell wrote: > >
> > > > Here's the flow roughly outlined as I understand it from > > http://nagios.sourceforge.net/docs/2_0/networkreachability.html and > > experience on this list, perhaps there's something that's missing -- > > > > - Service on Host2 reports CRITICAL state > > - check_command for Host2 is run. > > - if Host2 state != Warning/Critical > > Send service alert > > Else > > Suppress service alert > > check_command for host2 parent is run > > if host2 parent state != Warning/Critical > > Send host warning/down alert for host2 > > Else > > Send host unreachable alert for host2 > > Check more parents > > Fi > > Fi > > > > > Thanks Marc. Are you saying that you can't suppress an alert that is > returned as Critical? That doesn't seem to match the docs, but it makes > a lot of sense re the problem I am having. Suppress an alert for who? Host2? If host2's parent is up and you've specified that you want to receive host down notifications for host2, you'll receive an alert. If host2's parent is down and you've specified that you want to receive host unreachable notifications, you'll receive an unreachable notification for host2, but not a down notification (it's unreachable, not down). If you don't care for either, don't specify them. -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
