<br><font size=2><tt>Chris Neumann <chris@asterdata.com> wrote on
01/26/2007 11:44:42 AM:<br>
<br>
> Joe,<br>
> <br>
> Were all four of your graphs generated from the same RRD, or were
<br>
> they each from a different RRD<br>
> with a different scale (i.e. hourly, rolled up to daily, rolled up
<br>
> to monthly, etc.?)</tt></font>
<br>
<br><font size=2><tt>Same RRD.</tt></font>
<br><font size=2><tt><br>
> <br>
> In my case, I have data collected and stored in 1 second slots. <br>
> Thus, a one-day graph would have<br>
> 86,400 slots. When graphing, I might use the entire RRD or just
a <br>
> subset of the domain (such as the<br>
> last 10 minutes - 600 slots, by specifying appropriate parameters
<br>
> for --end and --start). What I've<br>
> found is unless I "zoom in" enough (restrict the graph's
domain <br>
> using --end and --start), the VRULEs<br>
> aren't drawn. My suspicion is that if the domain gets too large,
<br>
> rrdtool graph will not display the<br>
> VRULEs, as they have a fixed "width" of one slot (e.g. one
second, <br>
> in my case). How does this<br>
> compare to what you've been doing?</tt></font>
<br>
<br><font size=2><tt>The widest set of points I plot is 365 1-day points.</tt></font>
<br>
<br><font size=2><tt>A one-day graph in your case would need a width of
86400 pixels, and that sounds pretty big. So maybe rrdgraph 'fudges' when
the specified graph width is smaller than the number of plotted points.
And then it just skips 'fudging' the VRULE onto the graph. (?)</tt></font>
<br>
<br><font size=2><tt>Joe</tt></font>
<br>