Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #11654] Flapping detection enabled but notifications sent #4150
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11654
Created by jamacias on 2016-04-21 23:20:09 +00:00
I upgraded Icinga to version 2.4.4 and learned that bug #9969 is still present. I used the rpm repository to upgrade. I get PROBLEM
max_check_attempts = 3
flapping_threshold = 3
this is the simple script that I used at the host in order to trigger the alert:
I'm also attaching the script used at the server
2016-05-31 15:51:45 +00:00 by (unknown) b2e7747
2016-06-09 12:28:46 +00:00 by (unknown) 754638e
2016-06-13 08:43:57 +00:00 by (unknown) 8808e70
Updated by mfriedrich on 2016-04-22 07:58:47 +00:00
Please verify that flapping is active (e.g. by querying the API for that object in a defined interval). In addition to that check the debug logs for suppressing notifications due to flapping detection.
Updated by jamacias on 2016-04-23 00:05:17 +00:00
I am sending you the information requested.
*** indicates FLAPPINGSTART for the object in question. This occurs at 016-04-22 16:12:08
3.) debug.log - this is the complete debug.log
I noticed a very important observation: Even though the Icinga2 Web GUI already indicates "Currently flapping with a 13.00% state change rate" for the object, and the debug.log also indicates FLAPPINGSTART for the same object, the same API object being queried still indicates a parameter flapping false
Updated by mfrosch on 2016-05-31 14:50:19 +00:00
It seems like there is an odd problem with hard/soft states when returning to okay.
Which basically blocks any flapping detection if the max_check_attempts != 1
In addition, we need to further test and document flapping.
Updated by jamacias on 2016-12-02 22:08:45 +00:00