Action madness

[oliverm]

Hi gang,

I have a problem with actions. They seem to be doing some weird things.

Firstly, we have had a number of servers go down this weekend, but we didn't have any emails through. We have an action that says;

Type of calculation (A) and (B)
Conditions
(A) Trigger = "Ping to server"
(B) Trigger value = "TRUE"

The "Ping to server" trigger is TRUE currently for all the affected servers, but no action has been actioned and no email received (checking the historical actions list). Thats the first oddity which is quite serious really.

Secondly we have an alert that targets a specific trigger and again isn't firing. It does however fire for a completely unrelated trigger.

Type of calculation (A) and (B)
Conditions
(A) Trigger = "Server Template_Windows is unreachable"
(B) Trigger value = "TRUE"

and yet, the following action appears in the historical actions list;

Subject: Processor load is too high on <HOSTNAMEHERE>: ON
Processor load is too high on <HOSTNAMEHERE>: ON

2007.08.27
97889
{PROFILE}
*UNKNOWN*
*UNKNOWN*

I know that this is based on the above alert coz the {PROFILE} string only appears in the "Server Template_Windows is unreachable" alert.

Why would this be happening? It's not so bad that an action is firing for the wrong alert AS LONG as its firing the right alert as well. Having an alert that should be firing not fire is clearly very bad.

I can't see anything wrong with the config of the two alerts as we tested them when we created them and they seemed to work then.

Olly

[oliverm]

Any suggestions about this ? Any new actions also seem to fire on completely incorrect triggers.

Olly

[oliverm]

Any comments on this? We have actions firing off all over the place. A client just got an email about MY server despite the action being (A) AND (B) for A=trigger name <their server trigger> B=TRUE. It should be alerting on their server only, but it sends them alerts for ANY server and ANY trigger !!!!


ARRRGHHH

[Alexei]

I believe you hit a problem with action conditions which was already fixed in 1.4.1. Anyway I would suggest upgrading to 1.4.2.