[rrd-users] delayed updates
mperham at gmail.com
Tue Nov 13 18:41:23 CET 2007
Jason, thanks. We considered that but it's not ideal:
1) Metric data is less valuable over time. If it takes us 2 days to
recover, starting with the oldest data, our customers will be
screaming to know how their systems are performing NOW.
2) The amount of metric data is potentially huge so we need to
throttle the catch-up process or it will be very easy to spike our
No way around this limitation?
On 11/13/07, Jason Fesler <jfesler at gigo.com> wrote:
> > older data. If we push current data into an RRD file, is it possible
> > to push older data into it since the lastupdated timestamp will be
> > greater? Is it possible to fill in the gap without having to send all
> > the old data at once?
> Nope. SEnd the oldest data first. Maybe don't send it all at once - but
> record into rrd from your queue oldest first.
> If the data is too much, you might consider a max amount that you'll keep
> in the queue, and if you queue more, drop older entries (creating a gap)
> but once your system is back online and catches up you'll have recent
More information about the rrd-users