[rrd-users] Absolute values..

Gavin Landon Gavin.Landon at ignitetech.com
Tue Nov 18 16:07:15 CET 2008

You're the man..  Thank you for spending so much time explaining this to
me.  I think I have a good understanding now.

-----Original Message-----
From: rrd-users-bounces at lists.oetiker.ch
[mailto:rrd-users-bounces at lists.oetiker.ch] On Behalf Of Alex van den
Sent: Monday, November 17, 2008 7:57 PM
To: rrd-users at lists.oetiker.ch
Subject: Re: [rrd-users] Absolute values..

----- Original Message -----
From: "Alex van den Bogaerdt" <alex at vandenbogaerdt.nl>
To: <rrd-users at lists.oetiker.ch>
Sent: Tuesday, November 18, 2008 2:36 AM
Subject: Re: [rrd-users] Absolute values..

Sorry, part of it was confusing. Or rather I was confused.

I had "--step 1" and steps per RRA entry multiplied by 60 in my mind,
but I 
did not write this down.

If you stay with "--step 60", the rate stays 0.5 even when using min or

When you change to step 1, and have 60 times more steps in each RRA
the same amount of time is kept per entry.  But when you change average
max (or min) the combined 60 entries will be the maximum (or minimum)

But, depending on what you are actually monitoring, this may result in 
fooling yourself and/or others.  Why? Because you alter true data into 
something which is looking like, but not equal to, the truth. Data which

should have been zero becomes one, or vice versa.

Perhaps you are monitoring an on-off switch or alike.  Or a door 
open/closed, true/false, and so on. It makes sense to have fractions in
a case.  The door was open during 10% of the day. The switch was on half
the time.

Take a step back and think about what it actually is you want to make 
visible.  Do so keeping in mind that RRDtool will consider numbers to be
rate, "whatever per second".  It doesn't know nor care what this
is, it could even be "degrees celsius times 1 second" which then results
"degrees celsius times 1 second per second -> degrees celsius".  It
still is 
a rate.

Also think about consolidation. What will happen when you are looking at
graph representing a full year or more?  If you frequently see a 1 but
frequently a 0, MAX is going to make your data 1 throughout the year and
is going to make your data all zero.

If the amount of 1 is rather small, MAX will definately make it visible
the year graph but having one 1 during an hour on a day graph will show
as one 1 during a full day on a year graph.

If you do store rates like "the door was open 10% of the day", you (or 
rather rrdtool) can add such percentages and combine multiple rates into
rate valid during a larger time span. That's what consolidation is all 
about.  You usually don't want to know that the door was opened
somewhere in 
the year. Usually you want to know it was open 10% of the year.

And what happens if the data can become more than 1?  Can it in your 
application, once you're out of the development phase?  If so, you
start using such rates right away IMHO.

rrd-users mailing list
rrd-users at lists.oetiker.ch

More information about the rrd-users mailing list