ok => warn => crit => warn => crit (notifications)

[Rainer]

Nagios keeps resending notifications when a service goes in this state 
sequence:

ok => warn => crit => warn => crit

It sends 1 notification in the first critical state, and then another 
notification on the second critical notification.

Real world example:
Ping time in one host goes from:
15 ms (ok) => 100 ms (warning) => 300 ms (critical)
here it sends one notification, so far so good
then
300 ms (critical) => 150 ms (warning) => 300 ms (critical)
it sends ANOTHER notification.

How can I avoid this?
I know what state flapping is, but state flapping is a different concept 
(ok => critical => ok).

PS: the service notification_options is c,r

Rainer



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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