You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New Feature requests:
Please add a new object definition option, to Nagios core that would have a way for any notification definitions like "notification_options," "host_notification_options," and "service_notification_options" to be able to send contacts flapping start notifications without sending a flapping stop Notification to the contact.
Rational:
We are currently setting up a 3rd party issues tracking system and when an issues is escalated to the issue tracking system it creates a new issue, since we want that tracking system to be notified when a host/service is flapping we currently have to have Nagios send both the flapping start messages and the end message which by default creates to items with the flapping end notices flapping happening potentially hours later after we have potentially fallen back asleep, due to flapping being based on % of failures falling low enough.
Additional notes:
I am not requesting you created the converse option to where there is an option that only sends flapping stop notices, as I don't see a need for such an option for myself and I have not come up with a case where I could think of someone caring if flapping has come to a stop without caring if it started.
We are going to also be working with vendor of the issues tracking system vendor to come up with a way that the issues tracking systems doesn't create a new issues when flapping stop notices come in, but really Nagios core/XI should have a way to make to so that we don't send those notifications in the first place and have other systems/our intermediary infrastructure, expending cycles to communicating/process/drop those unwanted flapping stop notification to the issues tracking system.
The text was updated successfully, but these errors were encountered:
New Feature requests:
Please add a new object definition option, to Nagios core that would have a way for any notification definitions like "notification_options," "host_notification_options," and "service_notification_options" to be able to send contacts flapping start notifications without sending a flapping stop Notification to the contact.
Rational:
We are currently setting up a 3rd party issues tracking system and when an issues is escalated to the issue tracking system it creates a new issue, since we want that tracking system to be notified when a host/service is flapping we currently have to have Nagios send both the flapping start messages and the end message which by default creates to items with the flapping end notices flapping happening potentially hours later after we have potentially fallen back asleep, due to flapping being based on % of failures falling low enough.
Additional notes:
I am not requesting you created the converse option to where there is an option that only sends flapping stop notices, as I don't see a need for such an option for myself and I have not come up with a case where I could think of someone caring if flapping has come to a stop without caring if it started.
We are going to also be working with vendor of the issues tracking system vendor to come up with a way that the issues tracking systems doesn't create a new issues when flapping stop notices come in, but really Nagios core/XI should have a way to make to so that we don't send those notifications in the first place and have other systems/our intermediary infrastructure, expending cycles to communicating/process/drop those unwanted flapping stop notification to the issues tracking system.
The text was updated successfully, but these errors were encountered: