Help with an Alert Complex Condition to Work

Mike_Lomax

I am trying to build an Alert Complex Trigger Condition and just like other times I have tried to do this, I am not having any luck.  Hoping someone with experience with these can help.

Basically if any of all of the 4 servers in the first section are Down and a 5th server in the second section is Up, trigger the Alert.

I have simplified this down to having:

• A first section with a scope OR block containing 4 Nodes that are currently down in our environment.  The trigger condition in this first section uses an AND block and is Node Status is equal to Down.
• The section divider is AND and the second section scope is a AND block with one Node listed that I know is Up.  The trigger condition in this second section is Node Status is equal to Up.
• I don't have "Condition must exist for..." or "Alert can be triggered if..." checked in either section.
• The Reset Condition is simply set to "Reset this alert when trigger condition is no longer true" and
• Time of Day is set to "Alert is always enabled..."
• "Evaluate the trigger condition every" is set to 16 seconds.
• Alert Definition is Enabled.

I would expect, when this is saved to, to see an Alert appear in the Active Alerts list within 16 seconds or so but nothing after 10 minutes even.

I did test just the first section and the Summary page said that the 4 down Nodes would trigger Alerts.  I also tested just the second section and the Summary page said that 1 Up Node would trigger an Alert.

Here is the Trigger Conditions page:

So what am I doing wrong?

Mike_Lomax

Hold off on responding to this.

A while back I had an issue where new Alert Definitions I had created would not trigger.  SW Support tested in their lab and also could not get them to trigger.  They then created a new Alert Definition with the same configuration and it triggered.  They told me they felt the Alert Definitions I had previously created were corrupt and to try recreating them from scratch, like they had done.  That worked.  However it now appears that issue may be back.  Opening a new SW case for this.