New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #7071] Re-design passive checks and freshness #1951
Comments
Updated by gbeutner on 2014-09-05 13:13:25 +00:00
|
Updated by gbeutner on 2014-09-05 13:14:17 +00:00
|
Updated by mfriedrich on 2014-09-16 09:22:22 +00:00
|
Updated by mfriedrich on 2014-09-16 10:19:19 +00:00
|
Updated by mfriedrich on 2014-11-24 14:02:38 +00:00
|
Updated by mfriedrich on 2015-01-26 15:05:56 +00:00
|
Updated by mfriedrich on 2015-04-03 16:30:10 +00:00
|
Updated by tobiasvdk on 2015-04-22 12:05:13 +00:00 How about adding a boolean attribute
|
Updated by mfriedrich on 2015-05-18 08:14:42 +00:00
|
Updated by mfriedrich on 2015-06-22 14:52:51 +00:00
|
Updated by mfriedrich on 2015-06-23 13:36:38 +00:00
|
Updated by mfriedrich on 2015-07-07 12:36:19 +00:00
|
Updated by mathiasaerts on 2015-11-23 17:24:05 +00:00 Any chance this can be included in 2.5.0? The unknown check results are really frustrating every time Icinga is restarted.. |
Updated by mfriedrich on 2016-03-04 16:52:55 +00:00
|
Updated by mfriedrich on 2016-03-04 16:53:21 +00:00
|
Updated by tclh123 on 2016-03-07 08:07:16 +00:00 Hi @dnsmichi, |
Updated by elippmann on 2016-06-14 09:54:27 +00:00 Hi, 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. Best regards, |
Updated by mfriedrich on 2016-11-09 14:59:57 +00:00
|
@lippserd Is this still relevant? |
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
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2016-11-09 14:59:57 +00:00 (in Redmine)
=> Monitoring Basics
Relations:
The text was updated successfully, but these errors were encountered: