Module: check_mk
Branch: master
Commit: 1baa873feb3dd519f10a38864e13378c0d877789
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=1baa873feb3dd5…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Wed Aug 24 22:44:27 2011 +0200
Updated bug entries
---
.bugs/128 | 40 +++++++++++++++++++++++++++++++++++++---
1 files changed, 37 insertions(+), 3 deletions(-)
diff --git a/.bugs/128 b/.bugs/128
index 9ee272f..e0f9ef0 100644
--- a/.bugs/128
+++ b/.bugs/128
@@ -1,11 +1,45 @@
Title: df trends: Peak values after changing the trend_range
Component: checks
-Benefit: 1
State: open
-Cost: 2
-Date: 2011-02-10 09:45:24
Class: bug
+Date: 2011-02-10 09:45:24
+Benefit: 1
+Cost: 2
+Fun: 0
After changing the trend_range to a larger time the check reports a peak
value which is wrong. It might be needed to detect such a change and reset
the values.
+
+I've investigated this. The current behaviour is correct.
+In our demo server there was a filesystem with a trend
+of aprox. 800 MB/24h. This was nicely visible in the trend
+graph, with a light descending slope. I now increased the
+trend range to 48h. Now the trend value "jumped" to aprox
+1600 MB/48h. This is - however - the same value as 800 MB/24.
+What's not nice about this is that in the graph it looks like
+a jump.
+
+A possible solution would be to normalize the graph to
+MB/day, even if the trend range is for example one week.
+
+==> RESOLUTION:
+
+I think we'll make it like this:
+
+df.include: the performance data growth and trend will both
+be normalized to MB/24h - regardless of the trend_range
+parameter.
+
+PNP template: the graphs will be updated. The growth graph
+will be scaled to MB per *minute*. When painting the avg, last
+and max we can also print MB / 24h sec as an additional information.
+This information is only relevant to the user - however - if the
+growth is very static.
+
+In the migration notes we have to describe this. The performance
+data will be inconsistent if the user has used an other trend
+range than 24h.
+
+We will do this after 1.1.11i3 is out.
+