tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5709 from bascarsija/fix/flapping-documentation-typo-5703 

fixes minor typos in flapping detection documentation
This commit is contained in:
Jean Flach 2017-10-30 17:42:58 +01:00 committed by GitHub
parent 9ba5b4f4b7 4433ecea52
commit aad100aa6a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/08-advanced-topics.md
View File

@ -295,7 +295,7 @@ provides the `includes` and `excludes` attributes to solve this issue.
preferred.
The following example defines a time period called `holidays` where
notifications should be supressed:
notifications should be suppressed:
object TimePeriod "holidays" {
import "legacy-timeperiod"
@ -415,15 +415,15 @@ Example output in Icinga Web 2:
Icinga 2 supports optional detection of hosts and services that are "flapping".
Flapping occurs when a service or host changes state too frequently, which would result in a storm of problem and
recovery notifications. With flapping enabled a flapping notification will be sent while other notifications are
suppresed until it calms down after receiving the same status from checks a few times. flapping can help detecting
recovery notifications. With flapping detection enabled a flapping notification will be sent while other notifications are
suppresed until it calms down after receiving the same status from checks a few times. Flapping detection can help detect
configuration problems (wrong thresholds), troublesome services, or network problems.
Flapping detection can be enabled or disabled using the `enable_flapping` attribute.
The `flapping_threshold_high` and `flapping_threshold_low` attributes allows to specify the thresholds that control
when a [host](09-object-types.md#objecttype-host) or [service](objecttype-service) is considered to be flapping.
The default thresholds are 30% for high and 25% for low. If the computed flapping value excedes the high threshold a
The default thresholds are 30% for high and 25% for low. If the computed flapping value exceeds the high threshold a
host or service is considered flapping until it drops below the low flapping threshold.
`FlappingStart` and `FlappingEnd` notifications will be sent out accordingly, if configured. See the chapter on