Try to catch on dx/dt instead of x. Thast means the alert only sends a mail when something changes not when something is out of order.
-- Arnold ----- Original Message ----- From: "Poetzel, Christopher J." <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 06, 2002 4:51 PM Subject: [smokeping-users] Alert External Script -- Rate Limiting of Alerts > > I am starting to dig into alerts and am finding them very useful. > Currently I am having Smokeping call an external Perl script, passing > The script the SmokePing variables, and having the script parse them, decide > Whom to mail an alert to, and then mail it off. > The problem I am having is flooding people's email/pagers with alerts. > It tends to annoy people very much when the get the same page over and over > Every five minutes until it gets fixed. > I would like be able to suppress an alert if it was triggered in the past > X hours so not to flood people's email pagers. > Has anyone tried to implement this in a script or have another approach on a > problem. > > For example, > > An alert like > > +lossdetect > type=loss > pattern = >10%,>10%,>10%,>10%>10% > comment = There is a serious connectivity issue with this machine. > > Will fire every five minutes if a machine that is set up with the > Alerts=lossdetect > Line goes down. > > Thanks, > > Chris poetzel > [EMAIL PROTECTED] > Argonne National Laboratory > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Help mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/smokeping-users > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/smokeping-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
