<div dir="ltr">Simon;<div><br></div><div>Thanks for your very swift reply.</div><div><br></div><div>I'm still digesting your reply but I do have a small query.</div><div><br></div><div>my rrdtool first <rrdfile> command keeps returning different timing after each rrdtool update.</div>
<div><br></div><div>Why is that so?</div><div><br></div><div>Shouldn't it ALWAYS return the Unix time stamp for the first entry?<br><br>Deepest Regards</div><div>Steven Sim</div><div class="gmail_extra"><br><div class="gmail_quote">
On Tue, Jul 1, 2014 at 7:43 PM, Simon Hobson <span dir="ltr"><<a href="mailto:linux@thehobsons.co.uk" target="_blank">linux@thehobsons.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Steven Sim <<a href="mailto:unixandme@outlook.com">unixandme@outlook.com</a>> wrote:<br>
<br>
> I intend to process a data file each day but create the rrd database on the FIRST day of the month.<br>
><br>
> The creation shall ensure sufficient data points in the first day to contain the entire month but plot daily graphs until the end of the month, whereby it will plot the entire month.<br>
><br>
> Say for example,<br>
><br>
> If i had a step interval of 15 minutes (900 seconds),<br>
><br>
> rrdtool create $RRDB --step 900 --start $STARTIME \<br>
> DS:......<br>
> DS:......<br>
> .<br>
> .<br>
> .<br>
> DS:......<br>
> DS:......<br>
> RRA:AVERAGE:0.5:1:2880<br>
><br>
> 2880 = 24 hours x 4 data points per hour x 30 (thirty days in a month)<br>
><br>
> 4 data points since one hour has 4 data points (15 minutes step).<br>
><br>
> Would the above be correct?<br>
<br>
Yes, your numbers are correct, but I wonder about your methodology. It might help if you said what you are trying to achieve, because it's a rather unusual way of using RRD. Normally, you simply create one RRD that collects, stores, and consolidates the data you want. Typically this means keeping high resolution data for a shortish time, and keeping progressively lower resolution for progressively longer times - eg most applications don't need to keep (say) 5 minute resolution traffic data for 2 years ago. That's not to say you can't keep several years worth of high-resolution data if you want to.<br>
<br>
By keeping separate RRD files for each 'month', you'll find that it's hard work if you later want to do a graph for a year ! You'd also need to lock your "filled" data files otherwise one update to the wrong file could wipe out all the data.<br>
<br>
_______________________________________________<br>
rrd-users mailing list<br>
<a href="mailto:rrd-users@lists.oetiker.ch">rrd-users@lists.oetiker.ch</a><br>
<a href="https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users" target="_blank">https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users</a><br>
<br>
</blockquote></div><br></div></div>