[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Getting doubled alerts
- To: <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] Getting doubled alerts
- From: "Brehm, Scott" <sbrehm (at) titan.com>
- Date: Fri, 7 Oct 2005 12:05:46 -0700
- Thread-index: AcXLYRG7AV23+nRNTD+IO7Qw9uKsAgAEOpGg
- Thread-topic: [hobbit] Getting doubled alerts
Food for thought. Thanks
Scott Brehm
IT Manager
L3 Communications - Titan (ATS/ATAG)
3394 Carmel Mountain Rd, San Diego CA, 92121
858-720-4035
> -----Original Message-----
> From: Henrik Stoerner [mailto:henrik (at) hswn.dk]
> Sent: Friday, October 07, 2005 10:03 AM
> To: hobbit (at) hswn.dk
> Subject: Re: [hobbit] Getting doubled alerts
>
> The STOP condition triggers when it is used - i.e. it will only have
> effect for "conn" tests, since it is inside a rule that has
> "SERVICE=conn". But if you need to alert person2 and person3 of "conn"
> problems, then you cannot use the STOP keyword.
>
> Another way to avoid the duplicate alerts might be to restrict your
> general rule to not include the two special hosts:
>
> HOST=* EXHOST=atscm,atcsc SERVICE=conn
> MAIL sbrehm (at) titan.com COLOR=red
>
> HOST=%atscm
> MAIL sbrehm (at) titan.com COLOR=red
> MAIL person2 (at) titan.com COLOR=red
>
> HOST=%atscs
> MAIL sbrehm (at) titan.com COLOR=red
> MAIL person3 (at) titan.com COLOR=red
>
> So ... several ways of doing the same thing. You choose which one
> matches your thinking best :-)
>
>
> Regards,
> Henrik
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk
>
>
>