<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38"> <TITLE>RE: [Nagios-users] NAGIOS Notification Anomaly: Missing HOST UPNotification</TITLE> </HEAD> <BODY>  Thanks very much for your illuminating reply, Marc :-) You've renewed my faith in reading the manual! Many Thanks, Traiano -----Original Message----- From: nagios-users-bounces@lists.sourceforge.net on behalf of Marc Powell Sent: Thu 9/18/2008 2:25 PM To: nagios-users Mailinglist Subject: Re: [Nagios-users] NAGIOS Notification Anomaly: Missing HOST UPNotification On Sep 18, 2008, at 6:07 AM, Traiano Welcome wrote: > > I wonder if it may have something to do with the "host flapping" > and "service flapping" alerts occurring at the time the notification > should have been sent out? Yes, flapping suppresses notifications. See the Service and Host Filters section of <A HREF="http://nagios.sourceforge.net/docs/2_0/notifications.html">http://nagios.sourceforge.net/docs/2_0/notifications.html</A> as well as notification options for your service and contact if you want to receive notifications of flapping to know when it's stopped. -- Marc ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world <A HREF="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&url=/</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </BODY> </HTML>