[rrd-users] Question about RRDTool ..

[Felix Castillo Sanchez]

> -----Ursprüngliche Nachricht-----
> Von: rrd-users-bounces at lists.oetiker.ch [mailto:rrd-users-
> bounces at lists.oetiker.ch] Im Auftrag von Jean-Yves Avenard
> Gesendet: Donnerstag, 20. März 2008 08:43
> An: rrd-users at lists.oetiker.ch
> Betreff: Re: [rrd-users] Question about RRDTool ..
> 
> Hi again
> 
> On Thu, Mar 20, 2008 at 3:09 PM, Jean-Yves Avenard <jyavenard at gmail.com>
> wrote:
> > timestamp    local             remote
> >
> >  1205895600:  1.2642200000e+03  1.6115000000e+02
> >  1205906400:  1.2642200000e+03  1.6115000000e+02
> >  1205917200:  1.2642200000e+03  1.6115000000e+02
> >  1205928000:  1.2642200000e+03  1.6115000000e+02
> >  1205938800:  1.2642200000e+03  1.6115000000e+02
> >  1205949600:  1.2642200000e+03  1.6115000000e+02
> >  1205960400:  1.2642200000e+03  1.6115000000e+02
> >  1205971200:  1.2661600000e+03  1.6115666667e+02
> >  1205982000:  1.2350157481e+03  1.4383395556e+02
> >
> >
> >  As you can see, it has stored the value 1235 and 143.
> >  What happened to my 1209.49 and 124.98 ??
> 
> 
> I think I have identified where the problem lies.
> 
> The timestamp needs to be a multiple of the frequency, being in the
> EST time zone (GMT+11) it means that all my values gets transformed
> for some reason, I'm not sure on how they are calculated.
> If I re-entered my time and make sure the the timestamp are a multiple
> of 10800 (3 hours) in the GMT zone, then the value gets plotted
> properly and displayed as it should.
> 
> This sounds like a bug to me. You can not use RRD to use a timeframe
> like 3 hours in your own timezone otherwise the value retrieved will
> be transformed (but I don't know how).
> 
> Any ideas on how to get around the problem ?
> 
> Thank you
> Jean-Yves
> 
> _______________________________________________
> rrd-users mailing list
> rrd-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

Hi 

This is not an error. I thought the same but the reason is that rrdtool
interpolates the given value based on the step compared to the one before. 
Only if you have absolutely STEP seconds between data points it will take
the given value. 

After reading this in the documentation I think it is right way because when
collecting automatically you'll probably never get exactly the defined STEP!


Felix