Steve's right. Separate RRD's would be the way forward to ensure DS consistency. As a suggestion, why not write something which scrapes these RRD's periodically and collates the last DS value and drops it into a single RRD with multiple DS's…?
I've always found RRDTool::OO to be particularly friendly From: Steve Shipway <s.ship...@auckland.ac.nz<mailto:s.ship...@auckland.ac.nz>> Date: Thursday, 17 October 2013 21:22 To: 'Patrik Åkerfeldt' <patrik.akerfe...@gmail.com<mailto:patrik.akerfe...@gmail.com>>, "'rrd-users@lists.oetiker.ch<mailto:'rrd-users@lists.oetiker.ch>'" <rrd-users@lists.oetiker.ch<mailto:rrd-users@lists.oetiker.ch>> Subject: Re: [rrd-users] Post to individual data sources with multiple update requests >I would like to have one RRD file with all my indoor temperatures. One DS per >room. My problem >is that I receive temperature updates as individual events, thus I would like >to update the DS's in >the RRD file with individual update calls. For this application, you need to have separate RRD files. You can still make a single graph holding data from multiple files; however since the data are coming in at different points in time, and you cannot add a vector to the RRAs until you have all the elements, you should have one RRD per sample. Steve ________________________________ Steve Shipway ITS Unix Services Design Lead University of Auckland, New Zealand Floor 1, 58 Symonds Street, Auckland Phone: +64 (0)9 3737599 ext 86487 DDI: +64 (0)9 923 6487 Mobile: +64 (0)21 753 189 Email: s.ship...@auckland.ac.nz<mailto:s.ship...@auckland.ac.nz> PPlease consider the environment before printing this e-mail : 打印本邮件，将减少一棵树存活的机会
_______________________________________________ rrd-users mailing list rrd-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
