[dev.icinga.com #12963] Flapping start notifications not always sent

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12963

Created by tontonitch on 2016-10-24 13:38:36 +00:00

Assignee: tontonitch
Status: Feedback
Target Version: (none)
Last Update: 2017-01-02 18:33:41 +00:00 (in Redmine)

Icinga Version: 2.5.4

---

Hi,

As I have some issues with flapping detection (missing flapping start and maybe notifications during flapping period), I'm trying to figure out how the flapping detection works and how to configure it correctly.
For the missing flappingstart notifications, please find an extract of the received emails from icinga2. As you can see, there are lots of flappingend but only a few flappingstart.

Trying to figure out how the flapping detection works and how to configure it correctly, I didn't find lots of information on that subject in the official documentation.
I found some discussions and issues,
https://monitoring-portal.org/index.php?thread/33068-benachrichtigungen-trots-flapping/&postID=214764&highlight=flapping\_thresh#post214764
https://lists.icinga.org/pipermail/icinga-users/2015-June/009657.html
https://dev.icinga.org/issues/11899
https://dev.icinga.org/issues/9642

So I guess the default value for flapping_thresh is 30. What does it mean exactly? In order to calculate the adequate value to set here.

Also, unfortunately the icingaweb2 interface doesn't handle flapping notification yet (https://dev.icinga.org/issues/12766). So the only way to check that flapping detection and notification behavior during flapping period are working correctly is to check icinga2 log file.

Best regards,
Yannick

Attachments

• missing_flappingstart_notifications.png tontonitch - 2016-10-24 13:37:12 +00:00

[icinga-migration]

Updated by tontonitch on 2016-10-24 13:42:03 +00:00

Sorry, I did a mistake. That issue is related to icinga2 and not icingaweb2.
Could someone move the issue? As I cannot do that (can only copy it).
Thanks

[icinga-migration]

Updated by jmeyer on 2016-10-25 06:18:51 +00:00

• Project changed from Icinga Web 2 to Icinga 2
• Category deleted 148

[icinga-migration]

Updated by mfriedrich on 2016-12-07 22:43:24 +00:00

• Category set to libicinga
• Status changed from New to Feedback
• Assigned to set to tontonitch
• Icinga Version set to 2

You might want to test the snapshot packages including some fixes.

[icinga-migration]

Updated by sru on 2017-01-01 19:00:45 +00:00

Can confirm that 2.6.0-1 does not send "FlappingStart" notifications (in my case all of that type are missing) whereas "FlappingEnd" notifications are sent relyable.

The notification object has "FlappingStart" listed.

What i do is:

• disable active checking of a service.
• use a shell script to submit passive state changes every 5 seconds via the API.
• increase that interval to 90 seconds - no change.

[icinga-migration]

Updated by sru on 2017-01-02 18:33:41 +00:00

The reason these flapping_start notifications do not go out is in `lib/icinga/checkable-check.cpp`
at line 372:

        /* Flapping start/end notifications */
        if (send_notification && !was_flapping && is_flapping) {
                /* FlappingStart notifications happen on state changes, not in downtimes */
                if (!IsPaused())

send_notification is false for soft states but the fact that the check is flapping may hinder it to ever reach a hard state.

For my understanding, flapping_start should be notified even in softstates because flapping is an indicator of
a malfunctioning check, so some person should get a notification about that.

[dnsmichi]

Will be continued in #4982.