I would prefer to perform the update with the data based upon the collected time (which is the correct time the metrics occurred i.e. sampled), not the time it is updated (stored) in the rrd which could be a 1 to 2 minute delay (or in the event of some backlog scenario could even be hours later).
Sure, I can correct the issue that all "batches" are processed in the proper time sequence from when they were gathered down to the sub-second level, but that still wouldn't fix the issue of the RRD itself forcing itself to store the data on a "now" basis when the update occurs -- View this message in context: http://rrd-mailinglists.937164.n2.nabble.com/Disabling-Last-Update-tp7580590p7580595.html Sent from the RRDtool Users Mailinglist mailing list archive at Nabble.com. _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
