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 #7071] Re-design passive checks and freshness #1951
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7071
Created by mfriedrich on 2014-09-03 19:18:34 +00:00
=> Monitoring Basics
Updated by mfriedrich on 2014-11-24 14:02:38 +00:00
Updated by tobiasvdk on 2015-04-22 12:05:13 +00:00
How about adding a boolean attribute
Updated by elippmann on 2016-06-14 09:54:27 +00:00
At the moment freshness checks are only executed if active checks are enabled. Our documentation may be a bit misleading here.
In my opinion it would be great to reintroduce the freshness_threshold from Icinga 1.x.
If active checks are disabled and the freshness_threshold has passed without any new passive check result, Icinga 2 will run the configured check command as a forced active check. This virtual expiration time is calculated from
Just for the records, the check_interval in terms of active checks disabled represents the interval in which Icinga 2 expects passive check results. If the check_interval has passed w/o any new passive check result, nothing will happen in Icinga 2. But Icinga Web 2 displays that the check result is late. The check_interval (and retry_interval) for disabled active checks have visual impact only.