[Nagios-devel] Flap Detection Notification in 2.0
Posted: Fri Apr 04, 2003 12:28 pm
Several users have suggested that Nagios send out notifications for
flapping starts/stops, and I have decided to include this in 2.0.
I don't think Nagios can do a good job of sending out flapping
notifications unless I add another notification option ('f') to the
config files to indicate that a host/service/contact should
send/receive these types of notifications.
If the new notification option gets added, its fairly easy to have
Nagios send out notifications to contacts when flapping begins and
ends. That could mean, though, that some contact gets bothered with
notifications about a host/service starting to flap when they
normally would not get notified about a problem. Consider this
example:
A service is configured to only have notifications sent out on
Critical, Recovery, and Flapping notifications. The service starts
to flap between warning and unknown states, thus resulting in a
notification to appropriate contacts. When the flapping stops the
service is in a warning state and another flapping stop notification
gets send out to contacts. Normally these contacts wouldn't have
been notified, since the service didn't wander into a critical state.
So that's a bit of a negative side effect. However, I don't think
its accurate (or mabye even feasible) to wait to send the flapping
start notification until the service wanders into a state for which
it has notifications enable (i.e. critical in this example).
What do people think of this? Does it sound reasonable to add a new
notification option ('f') to services and hosts for flapping
notifications, realizing that this might generate notifications when
there normally wouldn't have been any?
If I don't hear anything back on this in the next few days I'm
planning on adding the 'f' option as described.
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
flapping starts/stops, and I have decided to include this in 2.0.
I don't think Nagios can do a good job of sending out flapping
notifications unless I add another notification option ('f') to the
config files to indicate that a host/service/contact should
send/receive these types of notifications.
If the new notification option gets added, its fairly easy to have
Nagios send out notifications to contacts when flapping begins and
ends. That could mean, though, that some contact gets bothered with
notifications about a host/service starting to flap when they
normally would not get notified about a problem. Consider this
example:
A service is configured to only have notifications sent out on
Critical, Recovery, and Flapping notifications. The service starts
to flap between warning and unknown states, thus resulting in a
notification to appropriate contacts. When the flapping stops the
service is in a warning state and another flapping stop notification
gets send out to contacts. Normally these contacts wouldn't have
been notified, since the service didn't wander into a critical state.
So that's a bit of a negative side effect. However, I don't think
its accurate (or mabye even feasible) to wait to send the flapping
start notification until the service wanders into a state for which
it has notifications enable (i.e. critical in this example).
What do people think of this? Does it sound reasonable to add a new
notification option ('f') to services and hosts for flapping
notifications, realizing that this might generate notifications when
there normally wouldn't have been any?
If I don't hear anything back on this in the next few days I'm
planning on adding the 'f' option as described.
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]