Shinken Enterprise supports optional detection of hosts and checks that are flapping. Flapping occurs when a check or host change state too frequently, resulting in a storm of problem and recovery notifications. Flapping can be indicative of configuration problems (i.e. thresholds set too low) or real network problems.
When an element is detected to be flapping, its notification will be bloked until it came to a stable state (whatever it's UP/OK or DOWN/CRITICAL).
Whenever Shinken Enterprise checks the status of a host or check, it will check to see if it has started or stopped flapping. It does this by.
An element is determined to have started flapping when its percent state change first exceeds the high flapping threshold.
An element is determined to have stopped flapping when its percent state goes below the low flapping threshold (assuming that is was previously flapping).
Let's describe in more detail how flap detection works with checks.
The image below shows a chronological history of check states from the most recent 21 check. OK states are shown in green, WARNING states in yellow, CRITICAL states in red, and UNKNOWN states in orange.

The historical check results are examined to determine where state changes/transitions occur. State changes occur when an archived state is different from the archived state that immediately preceedes it chronologically. Since we keep the results of the last 21 checks there is a possibility of having at least 20 state changes.
In this example there are 7 state changes, indicated by blue arrows in the image above.
The flap detection logic uses the state changes to determine an overall percentage state change. This is a measure of volatility/change for the element:
Note: when calculating the percentage state change, the flap detection algorithm will give more weight to new state changes compare to older ones.
If for example the calculated percentage state change for en element is 31% it will then be compared against flapping thresholds to see what should happen:
Shinken Enterprise uses several variables to determine the percentage state change thresholds is uses for flap detection.
For both hosts and checks, there are high and low thresholds that you can configure.
This screenshot shows the variables that control the thresholds used in flap detection for an host.

When an element is first detected as flapping, Shinken Enterprise will:
When an element stops flapping, Shinken Enterprise will:
In order to enable the flap detection features in Shinken Enterprise , you'll need to:

In order to change the Flapping Thresholds for a specifc element, you'll need to:
