[Xymon] Feature Request - Alerting - ALLSTOP

Henrik Størner henrik at hswn.dk
Sun Dec 8 17:55:23 CET 2013

On 08-12-2013 16:51, Patrick Nixon wrote:
> So, in building out my ruleset for alerts, I have a CPU test for a group
> of hosts that I have configured to have a weekday and weekend set of
> alerts.   This is among other specific rules for other tests/hosts
> combinations
> Down the bottom, I have a catch all rule that I've had to add a decent
> set of exceptions to which just makes it all that much harder to read
> the rules.
> As far as I know, there is no way to stop progression through the rest
> of the alerts file for a specific alert block.
> Ie:
>   MAIL alert1
>   MAIL alert2
> HOST=*
>    MAIL alert3
>    MAIL alert4
> I would like to put an ALLSTOP after alert2 to stop alert3/alert4 from
> getting the CPU alerts.

There is a STOP command for alerts.cfg, but I think what you really want 
is to put an "UNMATCHED" on the last catch-all rule. Like

		MAIL alert3 alert4

See the alerts.cfg man-page for a description of how these flags work.



More information about the Xymon mailing list