> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Eric Frazier > Sent: Monday, September 24, 2007 7:09 AM > To: [email protected] > Subject: [Nagios-users] Suppressing notifications due to Unreachable state > due to parent config >
> I have a very basic host that tests a http connect on google.com and > yahoo.com from our office named, "CableRogers" > The hosts we monitor that are outside the office have CableRogers listed > as a parent with "parents CableRogers" in their configs. This seems to > have been done correctly since if I look at the status map, I see > CableRogers being the hub for ---> host1 host 2 host3 > > I also have a test which I am able to break that both breaks the test > for CableRogers and for host2, but regardless of the timing I still get > notifications from host2. I tried testing this by specifically causing Are these host or service notifications? Unreachable or Down? > CableRogers to break, then breaking host2, but I still get notifications > for host2 and there isn't a 'u' in site. 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 -- 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
