[rrd-developers] Re: Data Loss on non-contiguous updates

[Tobias Oetiker]

Lee,

you are no particularly fond of the minimal-required-heartbeat
option I gather ?

the reason rrdtool does not consider the first value supplied after
a long 'downtime' is that it always assumes that the new value has
been valid since the last time the database got updated ... since
you do not up-date the database less frequently than configured via
mrhb, rrdtool must assume that the value as such has no known
valid-time, it only sets a new start point ... in the case of a
COUNTER type DS the counter value gets stored to be used as a
starting point for the next calulation .

cheers
tobi


-- 
 ______    __   _
/_  __/_  / /  (_) Oetiker @ ISG.EE, ETL F24.2, ETH, CH-8092 Zurich
 / // _ \/ _ \/ /  System Manager, Time Lord, Coder, Designer, Coach
/_/ \.__/_.__/_/   http://people.ee.ethz.ch/oetiker +41(0)44-632-5286

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