[hobbit] alert macro and SERVICE rule
Charles Jones
jonescr at cisco.com
Tue Oct 16 00:01:57 CEST 2007
Not sure if it makes a difference, but the macros I use do not contain
any part of the alert commands. In other words, using your example, I
use the macros like so:
hobbit-alerts.cfg
-----------------
$patrickemail=ple at host.com
$chrisemail=ccolon at host.com
$ediemail=edi at host.com
HOST=pd-gis
MAIL $patrickemail RECOVERED
MAIL $chrisemail SERVICE=http RECOVERED
MAIL $ediemail SERVICE=status REPEAT=24h RECOVERED
I use similar to above with no problems. I think your problem is from
using alert keywords inside your macros.
-Charles
Mark Hinkle wrote:
> Hobbit 4.2.0 w/ all-in-one 2007-02-09
>
> Can you use a macro in the hobbit-alerts.cfg and use the SERVICE rule
> in addition? Not able to do so at this end...
>
> hobbit-alerts.cfg
> -----------------
> $patrickemail=MAIL ple at host.com RECOVERED
> $chrisemail=MAIL ccolon at host.com RECOVERED
> $ediemail=MAIL edi at host.com REPEAT=1440m RECOVERED
>
> HOST=pd-gis
> $patrickemail
> $chrisemail SERVICE=http
> $ediemail SERVICE=status
>
>
>
> Running "hobbitd_alert --dump-config" seems to just stop after the
> first macro replacement:
>
> -bash-2.05b$ ./server/bin/bbcmd hobbitd_alert --dump-config
> 2007-10-15 14:20:07 Using default environment file
> /usr/hobbit/server/etc/hobbitserver.cfg
> HOST=pd-gis
> MAIL ple at host.com FORMAT=TEXT REPEAT=30 RECOVERED
>
> -bash-2.05b$
>
>
> If I change/remove the "SERVICE=http" from the line w/ the $chrisemail
> macro (for instance make it "DURATION>30"), then it *will* parse that
> line, but stop at the next one with the "SERVICE" rule:
>
> - $chrisemail SERVICE=http
> + $chrisemail DURATION>30
>
>
> -bash-2.05b$ ./server/bin/bbcmd hobbitd_alert --dump-config
> 2007-10-15 14:26:27 Using default environment file
> /usr/hobbit/server/etc/hobbitserver.cfg
> HOST=pd-gis
> MAIL ple at host.com FORMAT=TEXT REPEAT=30 RECOVERED
> MAIL ccolon at host.com FORMAT=TEXT REPEAT=30 DURATION>30 RECOVERED
>
> -bash-2.05b$
>
>
>
> Am I getting this wrong somewhere? Thanks in advance.
>
More information about the Xymon
mailing list