Skip to content
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

Open
lausser opened this issue Jul 31, 2023 · 6 comments
Open

enable_flap_detection=0 seems to be ignored #434

lausser opened this issue Jul 31, 2023 · 6 comments
Labels

Comments

@lausser
Copy link

lausser commented Jul 31, 2023

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:

info {
created=1690813918
version=1.4.1
}
program {
modified_host_attributes=0
modified_service_attributes=0
...
enable_flap_detection=0
...
}

service {
host_name=snclient
service_description=os_windows_svc_check_Server
modified_attributes=2
...
is_flapping=1
percent_state_change=0.00
...

Also Thruk shows the flapping symbol. Shouldn't everything be 0 when enable_flap_detection in the naemon.cfg was disabled?

@nook24
Copy link
Member

nook24 commented Aug 14, 2023

Sounds like a bug to me

@nook24 nook24 added the bug label Aug 14, 2023
@sni
Copy link
Contributor

sni commented Aug 14, 2023

Disabling enable_flap_detection does not reset all existing flapping flags. It simply prevents new flapping flags from being set.
But i agree, it should not prevent notifications from being sent out.

@jacobbaungard
Copy link
Contributor

Isn't the flapping flag removed on the next check execution? If not, that would probably be sensible imo.

@sni
Copy link
Contributor

sni commented Aug 18, 2023

I don't think this is done aleady, but yes, that might be the way to go.

@sni
Copy link
Contributor

sni commented Feb 6, 2024

Thinking about it, simply resetting the flag might not be a good idea. The global enable_flap_detection flag can be (temporarily) changed by an external command.
So this would result in lots of "starting to flap" notifications again.

One way would be to check the global flag at least in the notifications logic.
Better than nothing, but this would still show the host/service as flapping in the UI unless
the UI checks the global flag as well.

Naemon simply cannot predict whether the enable_flap_detection is just temporarily disabled or forever.

@sni
Copy link
Contributor

sni commented Feb 6, 2024

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.
For example, each time a check result arrives, update the state history used for flapping detection with an OK untill the list is cleared. (But silently ignoring flapping stop notification)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants