[rrd-users] This isn't normalization

[Steve Shipway]

I think your problem is defining how big 1GB actually is.

If the data you're feeding defines it as 1024 x 1024 x 1024 then it will be larger than 1000 x 1000 x 1000, which is the way it will be defined by default.  Even worse you may be thinking of it as 1000 x 1000 K where 1K=1024...

When you call the RRD graph command, you can pass a parameter to specify how big 1K is -- if you use 1024 then you'll get 1G as 1024x1024x1024 which will likely give the value you expect.

Steve

Steve Shipway
University of Auckland ITS
UNIX Systems Design Lead
s.shipway at auckland.ac.nz
Ph: +64 9 373 7599 ext 86487


________________________________________
From: rrd-users [rrd-users-bounces+s.shipway=auckland.ac.nz at lists.oetiker.ch] on behalf of Evan Langlois [uudruid74 at gmail.com]
Sent: Friday, 24 October 2014 6:04 p.m.
To: rrd-users at lists.oetiker.ch
Subject: [rrd-users] This isn't normalization

OK, I'm using Cacti, but the problem seems to be in rrdtool, or rather
I'm not passing the right information.  I'm monitoring how much
bandwidth is available on a metered connection.  When the graph hits 0,
I'm out (and throttled).  Simple stuff.

The problem.  I have maximum 15GB per month of "anytime" data and 20GB
of "nighttime".  The graph is telling me that I have 14.95GB remaining
in the former and 20.38GB in the latter.  Now, how could it possibly be
giving me a value that is MORE than the greatest value being fed to it.
I am using GAUGE/LAST for everything.

Here is a clip from rrdtool info.  How do I use the last_ds values?
Those are the correct values.  Thats what I want graphed.  Thats what I
want to display.  I have no idea what the value lines are or what they
are so much larger than the real values (larger than the max).  I don't
see how normalization could inflate values.  Any help would be GREATLY
appreciated.