[rrd-users] Re: Problem on update

Alex van den Bogaerdt alex at ergens.op.HET.NET
Thu Jul 11 18:28:05 MEST 2002


Chris Raymond wrote:

> As I see it, RRDtool is inserting BOGUS DATA.  In the example given,
> there is one real data point to insert, repeat, one.  It occurs at
> time 957481200.  This is on a 3600 second time update interval, but

[snip]

> I hope I've now made what I regard as a problem clear.  

I think this is an expectation problem.

You expect to insert a data POINT.  This is not what RRDtool does.
RRDtool inserts, with one update, a range.  This is from the last
update to the current update.

Let's see if you and I agree on the situation.  The numbers don't
necessarily match your examples:

step time:  3600
heartbeat: 36000

Updates:

   T+1*3600:   value 1
   T+2*3600:   value 2
   T+3*3600:   value 3
<long time>
   T+8*3600:   value 4

You expect the following to be inserted into RRDtool:

   at T+1*3600:  1
   at T+2*3600:  2
   at T+3*3600:  3
   at T+8*3600:  4

If above is *not* true then please try to rephrase your problem as
I clearly didn't understand in that case.  Also: stop reading now.

OK, you're still with me.  You expect the numbers to mean:

   at T+1*3600:  the time range between T+0*3600 and T+1*3600
   at T+2*3600:  the time range between T+1*3600 and T+2*3600
   at T+3*3600:  the time range between T+2*3600 and T+3*3600
   no updates    the time range between T+3*3600 and T+7*3600 --> NaN
   at T+8*3600:  the time range between T+7*3600 and T+8*3600

For "time range" you could read "point" in your understanding.

Same question:  Are we still in sync?  If not, please rephrase.

OK, still here.

This is what I expect the numbers to mean:

   at T+1*3600:  the time range between T+0*3600 and T+1*3600
   at T+2*3600:  the time range between T+1*3600 and T+2*3600
   at T+3*3600:  the time range between T+2*3600 and T+3*3600
   at T+8*3600:  the time range between T+3*3600 and T+8*3600

Why is this last line different?  At time T+8 I enter a number.
RRDtool hasn't seen any update between T+3 and T+8.  Therefore
it *must* assume the update is valid throughout the entire time
range *unless* this is larger than heartbeat.  This is how the
tool is designed.  Since heartbeat is more than (8-3)*3600, the
update is valid *for the entire range*.

Again, I think you shouldn't be reading this because I think you
will have bailed out at the 2nd decision point.

cheers,
-- 
   __________________________________________________________________
 / alex at slot.hollandcasino.nl                  alex at ergens.op.het.net \
| work                                                         private |
| My employer is capable of speaking therefore I speak only for myself |
+----------------------------------------------------------------------+
| Technical questions sent directly to me will be nuked. Use the list. | 
+----------------------------------------------------------------------+
| http://faq.mrtg.org/                                                 |
| http://rrdtool.eu.org  --> tutorial                                  |
+----------------------------------------------------------------------+

--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi



More information about the rrd-users mailing list