-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable_flap_detection=0 seems to be ignored #434
Comments
Sounds like a bug to me |
Disabling |
Isn't the flapping flag removed on the next check execution? If not, that would probably be sensible imo. |
I don't think this is done aleady, but yes, that might be the way to go. |
Thinking about it, simply resetting the flag might not be a good idea. The global One way would be to check the global flag at least in the notifications logic. Naemon simply cannot predict whether the |
Besides the quick fix from #452 we could think about slowly letting grow out the state history in case the host/service flapping flag is set, even if flapping detection is disabled. |
I have a naemon 1.4.1 (OMD 5.21.20230729-labs-edition) where i disabled flap detection globally.
But there is one service which is still shown as flapping (also in the logfile with
[1690795047] SERVICE NOTIFICATION SUPPRESSED: snclient;os_windows_svc_check_Server;Notification blocked because the object is currently flapping.
In the retention date one can clearly see the two different settings:
Also Thruk shows the flapping symbol. Shouldn't everything be 0 when enable_flap_detection in the naemon.cfg was disabled?
The text was updated successfully, but these errors were encountered: