Big Alerting Issue 🔗 link

Hi,

I have a problem where Hobbit is not properly sending alerts based on the
PAGE criteria. When I look at the info button for TESTHOST and TESTHOST1, it
*DOES* shows an alert to user-ba585fe8ccf7@xymon.invalid. When I run the test 'bbcmd
hobbitd_alert --test TESTHOST --color=red' or 'bbcmd hobbitd_alert --test
TESTHOST --color=red' it *DOESN'T' show that it matched an alert:

00023954 2006-12-10 21:14:51 Matching host:service:page
'TESTHOST:--color=red:' against rule line 314
00023954 2006-12-10 21:14:51 Failed 'PAGE=$SERVER1,$SERVER2 COLOR=red'
(pagename not in include list)

I also did a real test of taking the host down and no page went out and
nothing is listed in the /var/log/hobbit/notifications.log.

THIS IS URGENT IF ANYONE CAN HELP. I recently switched my alerts to be by
pagename and thought it should work based on the info page but I guess not.

Thanks.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SETUP

bb-hosts

page servers Servers
subpage wintel Wintel Servers
10.10.10.10     TESTHOST

page other Other
subpage othersub Other page
20.20.20.20     TESTHOST1

hobbit-alerts.cfg

$SERVER1=servers/wintel
$SERVER2=other/othersub

PAGE=$SERVER1,$SERVER2 COLOR=red
       MAIL user-ba585fe8ccf7@xymon.invalid RECOVERED

On Sun, Dec 10, 2006 at 09:27:14PM -0500, Geoff Hallford wrote:

The command is wrong, since you cannot have options after the hostname -
but you do need a columnname instead. Try

   bbcmd hobbitd_alert --test --color=red TESTHOST conn

I tried using your config files, and cannot reproduce the problem; I 
get the alert. Is this your entire hobbit-alerts.cfg ?


Regards,
Henrik

Hi Henrik,

This was a very downsized version. I have about 150 hosts I am monitoring
right now with extensive alerting. It's only the PAGE= alerting parameter
that is not working. I changed it to use HOST= today and it is working fine
but is obviously not the best way to do it.

With the HOST=, the testing command I used with --color=red after, actually
worked. It only didn't work with the PAGE=. Even in the notifications.log,
it showed sending alerts to only individuals *not* in the PAGE= alerting
items (i.e. using HOST= alerting options).

Thanks.

On 12/11/06, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:

-- 

'If my answers frighten you then you should cease asking scary questions.'
--Sam Jackson from Pulp Fiction

Hi Henrik,

This was a very downsized version. I have about 150 hosts I am monitoring
right now with extensive alerting. It's only the PAGE= alerting parameter
that is not working. I changed it to use HOST= today and it is working fine
but is obviously not the best way to do it.

With the HOST=, the testing command I used with --color=red after, actually
worked. It only didn't work with the PAGE=. Even in the notifications.log,
it showed sending alerts to only individuals *not* in the PAGE= alerting
items ( i.e. using HOST= alerting options).

Thanks.

On 12/11/06, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:

On Sun, Dec 10, 2006 at 09:27:14PM -0500, Geoff Hallford wrote:

I have a problem where Hobbit is not properly sending alerts based on
the
PAGE criteria. When I look at the info button for TESTHOST and

TESTHOST1, it

*DOES* shows an alert to user-ba585fe8ccf7@xymon.invalid. When I run the test 'bbcmd
hobbitd_alert --test TESTHOST --color=red' or 'bbcmd hobbitd_alert

--test

TESTHOST --color=red' it *DOESN'T' show that it matched an alert:

The command is wrong, since you cannot have options after the hostname -
but you do need a columnname instead. Try

   bbcmd hobbitd_alert --test --color=red TESTHOST conn

I tried using your config files, and cannot reproduce the problem; I
get the alert. Is this your entire hobbit-alerts.cfg ?


Regards,
Henrik

-- 
'If my answers frighten you then you should cease asking scary questions.'
--Sam Jackson from Pulp Fiction