Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
I have set up a host escalation that triggers at the 3rd notification of a certain host. When the host was first defined the notification count started at 0. So the escalation was triggered 3 notifications later and worked perfectly. But after that problem was resolved and the host stabilized the notification stayed at 5 and never reset. Even 3 weeks later when we have another issue the escalation happens immediately rather than waiting till the "third" notification (because the notification count never reset after the last problem resolved). How do I get the notification count to zero out every time the host stabilizes in an up state? I want the notification to go to the default contact the first 2 notifications and escalate on the 3rd FOR EACH PROBLEM. These problems should be separated by the host reaching a hard-up state.
What version of core is this? Do you see the current_state, last_state_change, last_hard_state_change, and last_time_* lines accurately update in /usr/local/nagios/var/status.dat when it goes back into an OK state?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
With my limited knowledge of what the values should be, all of the values you mentioned seem correct in `/usr/local/nagios/var/status.dat` before, during and after the very first problem my host has. However, after the first problem, the `current_notification_count` does not reset to zero. You can see this in the after portion here:
I've been able to reproduce this and currently pinging dev regarding it. Thanks for bringing it to our attention. I'll try to have an update for you as soon as possible.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.