Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8805
Created by rhillmann on 2015-03-18 21:52:10 +00:00
Since update to r2.3.0-1 the check "cluster-zone" displays the log lag.
Zone 'master' is connected. Log lag: 6 days, 14 hours, 7 minutes and 4 seconds
We have continously icinga2 service reloads, every 20min caused by puppet, but the log lag is still "behind" on our two master servers. We have seen the same problem on the other zones.
2015-09-25 12:24:45 +00:00 by mfriedrich 717118f
2015-09-25 12:28:01 +00:00 by mfriedrich c3a4744
Updated by rhillmann on 2015-03-19 08:11:18 +00:00
Updated by smadmin on 2015-04-10 13:13:21 +00:00
We can confirm this:
Updated by dgoetz on 2015-07-03 06:57:23 +00:00
Perhaps some hints on the problem, I found while playing with this check:
Updated by mfriedrich on 2015-09-25 12:23:11 +00:00
When the remote endpoint log position is 0, the lag difference is the current time which results in that output formatting.
Refactor the calculation into a function, since we use that for 2.4 inside the api status queries. Makes back porting harder, but who cares anyways.
Modified icinga2b's log position to 0, unpatched output: