Page 1 of 1
first_notification_delay does not suppress recovery alert
Posted: Mon Sep 24, 2018 4:44 pm
by fasterfourier
Hello, I have recently updated my Nagios 4.1.0 installation to 4.4.2. In some cases, I have a first_notification_delay directive configured for services. In the previous nagios version, it appears that both warning/critical AND recovery notifications were suppressed during the first_notification_delay period. In 4.4.2, it appears that only the literal "first" notification is suppressed, but a subsequent recovery is not. Therefore, we get random recovery alerts with no corresponding warning or critical alert if there is an outage and a recovery that both occur within the time defined in first_notification_delay.
Any ideas here for how to suppress these random recovery alerts?
Re: first_notification_delay does not suppress recovery aler
Posted: Tue Sep 25, 2018 1:03 pm
by scottwilkerson
I believe this to be resolved in the maint branch on Github
https://github.com/NagiosEnterprises/na ... tree/maint
Re: first_notification_delay does not suppress recovery aler
Posted: Tue Sep 25, 2018 2:17 pm
by fasterfourier
Is this what you're referencing?
4.4.3 - 2018-XX-XX
------------------
FIXES
* Fixed services sending recovery emails when they recover if host in down state (#572) (Scott Wilkerson)
If so, our case doesn't exactly match that since the host is not in the down state.
Re: first_notification_delay does not suppress recovery aler
Posted: Wed Sep 26, 2018 7:42 am
by scottwilkerson
It is but the description in the log doesn't list every case that was affected.
In reality, what was changed was we fixed prematurely sending recovery emails before all the rest of the logic that would have suppressed them was executed.
Re: first_notification_delay does not suppress recovery aler
Posted: Wed Sep 26, 2018 9:47 am
by fasterfourier
Gotcha. Thanks for the details--I'll give that a try.
Re: first_notification_delay does not suppress recovery aler
Posted: Wed Sep 26, 2018 9:55 am
by scottwilkerson
fasterfourier wrote:Gotcha. Thanks for the details--I'll give that a try.
Let us know if the problem persists