Hey Sven , thank you very much for you detailed information, I spent a few hours going thought some documents about aberrant yesterday and feel better now.<br><br>My current rrdtool is at version 1.0.49, which even does not support "updatev" argument, so I am not sure what the different between "update" and "updatev" will be, will install
rrdtool-1.2.19 today and do some test.<br><br>Thanks again!<br><br>Joh<br><br><br>On 5/3/07, <b class="gmail_sendername">Sven Ulland</b> <<a href="mailto:sveniu@opera.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sveniu@opera.com</a>> wrote:<div><span class="gmail_quote">
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><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 updatev'
<br>>> command, which will output FAILURE=1.0 (different syntax), if<br>>> it detects failures. FAILURE=0.0 if not. In other words, I parse<br>>> the output of the command, and trigger alerts based on it. You
<br>>> should probably implement a wrapper around the parsing/alarming,<br>>> so that you won't get flooded with mails/SMS messages every five<br>>> minutes while a deviation is happening.
<br>>><br>>> Sven<br></blockquote></div><br>