This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
[dev.icinga.com #5252] explain "Check results for service x on host y are stale by 0d 0h 0m 10s (threshold=0d 0h 10m 0s). Forcing an immediate check of the service..." #430
Labels
Milestone
This issue has been migrated from Redmine: https://dev.icinga.com/issues/5252
Created by mfriedrich on 2013-12-03 08:17:53 +00:00
Assignee: Wolfgang
Status: Closed (closed on 2014-01-13 19:56:21 +00:00)
Target Version: 1.11
Last Update: 2014-01-13 19:56:21 +00:00 (in Redmine)
the code part is as follows in base/checks.c
by default, the following applies
if the service has not been checked now, but in the past (event_start > last_check) and its freshness threshold is 0, max_service_check_spread multiplied by the interval is added as additional offset (happens during startup, in order to detect how fast the initial service check (and state + output) must happen.
As a user I would expect that explaination in http://docs.icinga.org/latest/en/servicechecks.html (couldn't find a better place with more generic check behaviour info)
The text was updated successfully, but these errors were encountered: