[rrd-users] Re: logging old data.... RRD update frequency....
Alex van den Bogaerdt
alex at ergens.op.het.net
Thu Apr 24 13:04:34 MEST 2003
On Thu, Apr 24, 2003 at 06:36:27AM -0400, Daniel A. Murray wrote:
> The script that starts the process also checkes to see if the results file
> exists, and if so, parses it and then passes it to RRD with the start and
> elapsed time as parameters.
> While this generally works ok, on occasion a wayward process sometimes takes
> longer than 5 minutes, and occasionally as long as 48 hours. The problem is
> how to accurately go back and log that data which, from an RRD pespective
> would have been missed.
Nope, from an RRD perspective, the data is known to be unknown. This is
different from what you expect, it is a known fact that the update wasn't
there while the next was. The data isn't missing, the data is known to be
> Any thoughts? The only way I can think of is a brute force method of
> exporting the entire RRD, inserting the data, then re-importing the entire
> RRD. There has to be a better way.
This is more difficult than you think. It doesn't fit the way RRD works.
Your numbers are normalized, then they are moved to each of the RRAs. You
will have to recalculate the input for these RRAs however you cannot do this
because the input isn't there anymore.
If this doesn't make any sense at all for you I suggest that you read my
stuff on rrdtool, available on faq.mrtg.org
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help mailto:rrd-users-request at list.ee.ethz.ch?subject=help
More information about the rrd-users