<div><div>Thanks for information, guys!<br><br>> Yes, you have to wait for one seasonal period before the HWPREDICT<br>> value is visible, and two periods before the deviation bars are there.<br><br>emmm, my current seasonal period is configured as 288, (RRA:HWPREDICT:1440:
0.1:0.0035:288 )<br>that means I will wait 2 days to get the upper|lower line, right?<br><br>I must have missed some important concepts here, could you point me where can I find more explanation about "two periods before the deviation bars are there"?
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This is a major hurdle when trying to tune the values, since it takes<br>days and even ways to try out new values every time. That is why you
<br>probably want to make some scripts that can quickly regenerate graphs.<br>There's something called hw-reapply that can do this for you, but I<br>haven't tried it, and I don't know if it shows immediate results:
<br><a href="http://rrfw.sourceforge.net/rrdman/">http://rrfw.sourceforge.net/rrdman/</a><br><br>What I do is to log all 'rrdtool update' commands to a file, so I<br>can easily run this file to repopulate the RRD files. Then I can tune
<br>the HW values when creating the RRD, run the backlog, and see graphs<br>immediately.<br><br>Also, I'd rather use a 1 day (or 7 days) season. A five day season<br>could have problems with deviations in week-ends. Depends on your
<br>traffic patterns, of course.</blockquote><div><br>Sure, mine is just a quick test, and when you say "season", you actually mean "array length", right? ;)<br><br>Thanks again!<br><br>Joh<br><br></div>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Sven<br><br><br>> On 5/4/07, *John Conner* < <a href="mailto:bs7799@gmail.com">bs7799@gmail.com
</a> <mailto:<a href="mailto:bs7799@gmail.com">bs7799@gmail.com</a>>><br>> wrote:<br>><br>> Hey Sven , thank you very much for you detailed information, I spent<br>> a few hours going thought some documents about aberrant yesterday
<br>> and feel better now.<br>><br>> My current rrdtool is at version 1.0.49, which even does not support<br>> "updatev" argument, so I am not sure what the different between<br>> "update" and "updatev" will be, will install
rrdtool-1.2.19 today<br>> and do some test.<br>><br>> Thanks again!<br>><br>> Joh<br>><br>><br>><br>> On 5/3/07, *Sven Ulland* < <a href="mailto:sveniu@opera.com">sveniu@opera.com
</a><br>> <mailto:<a href="mailto:sveniu@opera.com">sveniu@opera.com</a>>> wrote:<br>><br>><br>> Next, to actually have it report aberrant behaviour in real-time,<br>> as opposed to post-mortem, you'll need a wrapper script to run
<br>> 'rrdtool updatev' and parse the output. There are probably fancy<br>> bindings in perl for this, or some other graceful way of doing it.<br>> My way is a quick python script that parses the output looking for
<br>> 'FAILURES', and then determining if the corresponding value is<br>> greater than 0.0.<br>><br>> Well, that's pretty much it. Good luck!<br>><br>> Sven<br>
><br>><br>> > > I use the aberrant behaviour detection in rrdtool and I find<br>> > > it quite handy. To detect problems, i use the 'rrdtool<br>> updatev'
<br>> > > command, which will output FAILURE=1.0 (different syntax), if<br>> > > it detects failures. FAILURE=0.0 if not. In other words,<br>> I parse<br>> > > the output of the command, and trigger alerts based on
<br>> it. You<br>> > > should probably implement a wrapper around the<br>> parsing/alarming,<br>> > > so that you won't get flooded with mails/SMS messages
<br>> every five<br>> > > minutes while a deviation is happening.<br>> > ><br>> > > Sven<br>><br>><br>><br><br></blockquote></div><br>