[smokeping-users] question about 'someloss' alerts..

[B. Cook]

Hello Tobias,

Thank you for your email.

That did seem to help but I now see that I have some duplicate alerts, 
as I copied some down from the site as well.

Does the order that they are listed in matter?

As I am still getting the someloss alert.

Below is the order that the alerts appear in my config:

+bigloss
type = loss
# in percent
pattern = ==0%,==0%,==0%,==0%,>0%,>0%,>0%
comment = suddenly there is packet loss

+someloss
type = loss
# in percent
pattern = >0%,*12*,>0%,*12*,>0%
comment = detected loss 3 times over the last two hours

+startloss
type = loss
# in percent
pattern = ==S,>0%,>0%,>0%
comment = loss at startup

+rttdetect
type = rtt
# in milli seconds
pattern = <10,<10,<10,<10,<10,<100,>100,>100,>100
comment = routing mesed up again ?

+rttbadstart
type = rtt
# in milliseconds
pattern = ==S,==U
comment = offline at startup

+offstart
type = rtt
pattern = ==S,==U
comment = Box is offline at startup

+offline
type = rtt
pattern = !=U,==U,==U
comment = Box went offline

+online
type = rtt
pattern = ==U,==U,!=U
comment = Box went online


And this is the definition I have for my main menu item.

+ PCSD
menu = PCSD
title = Poughkeepsie City School District
remark = Words of wizdom here..
alerts = 
bigloss,someloss,startloss,rttbadstart,rttdetect,online,offline,offstart

Is the fact that someloss appears first in my alerts the reason that I 
get the the someloss messages and not the offline messages?


Tobias Oetiker wrote, On 6/1/07 9:56 AM:
> B,
> 
> the pattern you picked will trigger at much less pronounced loss
> cenarious than what you see ... the pattern says that you want an
> alert if there are three instances of loss mixed up with no-loss
> situations ...
> 
> to see if a line is don when you start smokeping, you can anchore a
> pattern at the 'start':
> 
> 
> +offstart
> type = rtt
> pattern = ==S,==U
> comment = Box is offline at startup
> 
> 
> +offline
> type = rtt
> pattern = !=U,==U,==U
> comment = Box went offline
> 
> +online
> type = rtt
> pattern = ==U,==U,!=U
> comment = Box went online
> 
> 
> Today B. Cook wrote:
> 
>> Hello,
>>
>> I've just added smokeping to a network that currently has 3 of it's
>> circuits (T1's) down.
>>
>> and I am continually bombarded with someloss alerts; But I think the
>> confusion is about how I am understanding the pattern for the alert.
>>
>> Pattern
>> -------
>>  > >0%,*12*,>0%,*12*,>0%
>>
>> Data (old --> now)
>> ------------------
>> loss: 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%,
>> 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%, 100%,
>> 100%, 100%, 100%, 100%
>> rtt: U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U, U,
>> U, U, U, U, U
>>
>> I am wondering if there is a better alert that i could make that would
>> indicate the obvious that the circuit was never up (yet) and that it is
>> still down.
>>
>> I guess I am wondering why the alert is called 'someloss' when there
>> actually is a total loss..
>>
>> I was wondering if someone else had an alert for 'totalloss' or
>> something better than someloss for this type of an alert/pattern.
>>