Tobias Oetiker wrote: > ~snip > > something like this would be rather simple to implement ... BUT > it would require a sensible interface in the config file. > > any ideas on this? > > cheers > tobi Maybe a priority parameter for each alert could be added... then Smokeping could do a check to see if a higher priority failure exists on the same device then it could know to not bother sending an email alert (though still logging to syslog would be ideal).
+OverFivePercent type = loss pattern = >5%,>5%,>5% priority = 3 comment = Three or more polls showing greater than 5% packet loss. +NoResponse type = loss pattern = ==100% priority = 2 comment = Host not responding on 1 (or more) consecutive intervals +OfflineAtStart type = rtt pattern = ==S,==U priority = 1 comment = Smokeping was restarted and this device was already off-line. Another nice parameter might be something to avoid returning a clear status email for items we want to know trigger an alert but we don't want to know when the pattern no longer matches. This would work well in the OfflineAtStart alert. Your thoughts? Thanks and Regards, Eric Brander -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/smokeping-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
