I believe that since edgetrigger is not set on someloss that it's overriding the priority setting. I can't imagine that this would ever be desirable so I'd think a bug report is the next step. That is, if you've tried it with edgetrigger on both monitors and off on both monitors to confirm. YMMV.,
On Thu, Jun 5, 2014 at 7:02 AM, Vladimir-M. Obelic <vobe...@gbit6.net> wrote: > Hi all, > > I'm using smokeping 2.6.8 and the priority option doesn't seem to work for > me. > > This are my alerts: > > > +someloss > type = loss > # in percent > pattern = >0%,*12*,>0%,*12*,>0% > comment = loss detected 3 times > priority = 2 > > +hostdown > type = loss > pattern = >60% > # send mails only on state change > edgetrigger = yes > comment = Massive loss for 5 mins > priority = 1 > > > Basically I'm continuing to get 'someloss' mail alerts after the hostdown > was triggered (obviously for same target). > > Here's the triggered mail alerts: http://pastebin.com/CzQucmSw > > Any clue why? Maybe related to the edgetrigger? > > BR, > Vladimir > > _______________________________________________ > smokeping-users mailing list > smokeping-users@lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > >
_______________________________________________ smokeping-users mailing list smokeping-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users