Yes, exactly. RRDtool will take care of rotating and expiring the data.
If your reason for multiple daily RRD files is to keep archives for longer, then simply extend the primary RRA to hold more than one day’s data. Steve Shipway [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Steven Sim Sent: Wednesday, 11 June 2014 9:56 a.m. To: Steve Shipway Cc: [email protected] Subject: Re: [rrd-users] If input is already in text format and I craft a perl script to parse the text format and update rrd database, what should the step and heartbeat be? Steven; The below will imply I keep updating the same rrd file every day and not use a different rrd file each day. Would the above be correct? Warmest Regards Steven Sim On Wed, Jun 11, 2014 at 5:14 AM, Steve Shipway <[email protected]> wrote: I don’t really understand why you think that you’d need to have separate RRD files for the ‘daily’ graphs and the ‘monthly’ one. Why not have a single RRD, with two RRAs – one with 1cdp=1pdp (that you use for your daily graph) and one with a higher granularity – maybe 1cdp=1hour=4pdp – that extends for 62 days (to allow a graph of the last and current calendar months). When you generate your graph, simply use the start and end params to specify that you’re making a daily or monthly graph, and the correct RRA should be used. This is how MRTG, Cacti and similar use RRDTool. As you add new data to the RRD, RRDtool will take care of the summarisation and expiry of data. If you want to archive daily data for longer, then simply extend the first RRA as far as required. Steve Steve Shipway [email protected]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
