[dev.icinga.com #11861] Document flapping

[icinga-migration]

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

Created by mfrosch on 2016-05-31 14:51:24 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2017-01-02 11:41:58 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

We need to document flapping, so a user understands what is going on, and what to expect from the available configuration.

---

Relations:

• relates #11654
• duplicates #11861

[icinga-migration]

Updated by mfrosch on 2016-05-31 14:51:33 +00:00

• Relates set to 11654

[icinga-migration]

Updated by mfrosch on 2016-07-05 09:33:48 +00:00

• Assigned to deleted mfrosch

[icinga-migration]

Updated by toupeira on 2016-09-16 18:34:35 +00:00

As a new Icinga2 user who's unfamiliar with both Icinga1 and Nagios, the current documentation is indeed very mysterious :)

The flapping algorithm used in Icinga 2 does not store the past states but calculates the flapping threshold from a single value based on counters and half-life values. Icinga 2 compares the value with a single flapping threshold configuration attribute named flapping_threshold.

I'd expect that flapping_threshold is the number of times consecutive checks have to change state to trigger FlappingStart, and then the number of times the state has to be stable in order to trigger FlappingEnd. Is that understanding correct? What's the default value?

Flapping detection can be enabled or disabled using the enable_flapping attribute.

This doesn't specify on which objects this can be applied, from example configurations I've seen it seems to be hosts and services?

[icinga-migration]

Updated by elippmann on 2016-12-16 11:43:32 +00:00

• Duplicated set to 13399

[icinga-migration]

Updated by sru on 2017-01-02 11:41:58 +00:00

provided docu update in #13827

[dnsmichi]

Will be continued in #4982.