Module: check_mk
Branch: master
Commit: ce0393b3b3eb47cd3f4bbfc27c2f781388f56ba1
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=ce0393b3b3eb47…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Fri Feb 15 14:37:09 2013 +0100
Updated bug entries #0900
---
.bugs/900 | 42 ++++++++++++++++++++++++++++++++----------
1 files changed, 32 insertions(+), 10 deletions(-)
diff --git a/.bugs/900 b/.bugs/900
index 5546662..3dc9cfe 100644
--- a/.bugs/900
+++ b/.bugs/900
@@ -1,12 +1,34 @@
-Title: Make multisite optional username from configured environment vars
+Title: Check_MK does not handle interval_length != 60 correctly
Component: multisite
State: open
-Date: 2013-01-22 14:49:10
-Targetversion: 1.4.0
-Class: feature
-
-For example X_FORWARDED_USER or REMOTE_USER should be usable as "user" within
-multisite. At the moment we only use req.user, which seem only to be set, when
-one really authenticated with the local webserver.
-In case of some reverse proxy setups and single sign on environments, this is
-not possible. Make it configurable, disabled by default!
+Date: 2013-02-15 14:30:58
+Targetversion: future
+Class: nastiness
+
+Reveived via feedback@:
+
+I'm normally using Nagios with the parameter "interval_length" set to
+"1". Despite the warnings in the config file I haven't expected problems
+with Nagios at all after adjusting all relevant parameters to reflect
+this change - but I'm now able to check services at a higher rate then
+only 1 minute.
+
+But IMHO check_mk does not reflect this change when displaying the
+service details. It seems that the values for " Service normal/retry
+check interval" are not correctly multiplied with the configured value
+for "interval_length" but (hardcoded?) with the default value of
"60".
+So in my environment all values are too high as by factor 60:
+
+Example given:
+
+interval_length = 1
+
+check_interval = 10--> check every 10 seconds
+
+retry_interval = 3--> retry after 3 seconds
+
+results in display within check_mk GUI:
+
+Service normal/retry check interval600s/180s
+
+It seems to be a bug in the display only, checks are running correctly.