SEUM Alerts are not being triggered?

If you remove the fields in Suppression does it work?  If it works when you do that, you may try adding the contents of your alert trigger to the suppression tab. 

it would then look like:

suppress when all

status is equal to down

     suppress alert when any

     recording ID is equal to ******

     recording ID is..........etc

Your issue is likely the misuse of alert suppression conditions. The Alert Suppression tab isn't for filtering alerts as you've done here, but is rather to define a condition that can't also exist in the same context as the trigger condition. It's used primarily for dependency alerting. E.G. Trigger Condition: Alert me When Node "X" is "Down". Suppression Condition: Unless Node "Y" is also "Down".

Your Alert Suppression condition as-written wouldn't make any sense as a Trigger Condition, and as such doesn't work as a Suppression condition. If you want to filter a subset of your recordings you'll need to do this as part of your trigger condition. Below is an example of how this is done.

Thank you both for your suggestions.  I believe after playing more with the advanced alerts and using aLTeReGo's suggestions that indeed the Alert Suppression tab is not intended to be used as filter.  I've change most of my alerts and they are working properly now except one that keeps giving me headaches.  This is another global/generic "Alert me if a Step has a status of Warning, Critical or Unknown" and then I added three Recording_IDs that I do not want included on this alert, but each time I try to get it to work I get email alerts for all my transactions with statuses of "Up" for every step.  When I remove the three Record_IDs I want to keep from being alerted on it works fine, but then it would be including those IDs, if they ever had one of those status.  I've tried put them in as None, Not ALL and All (but used not equal to) and nothing every time I get a slew of all Up status alerts.  Now I'm wondering why it was working fine all these months when I was using the alert suppression tab to filter out certain transactions.  I think I'm still struggling with how to setup the groups properly, even after reading the Admin Guide, (i.e. all = and statements and any = or statements etc..)  I understand that, but it doesn't seem to be working the way it suppose to. Anyway here's the screenshot of the one that I'm having issues with.

Thanks again,

Randall

The alert as you have it defined appears to be correct. Some things I would recommend double and triple checking.

Ensure your recording ID's are correct. I usually use "Name" so I can tell which recording is specified without having to hunt through the browser URL or debug logs.

Make certain you have nothing defined " for a reset trigger other than "Reset when trigger conditions are no longer true"

Clear anything configured under the Alert Suppression tab

Try re-creating the alert. There are multiple properties named "Status" so make sure you're using the one for Step.

If that doesn't help to resolve your issue then I recommend opening a case with support. They have some fancy troubleshooting tools that can break the alert down into its specific SQL query, which should shed some light on where the problem lies.

Thanks again aLTeReGo,

I checked all the settings, Recording IDs, nothing defined for reset action etc...  Then I tried deleting and re-creating the alert, this time I also used the Transaction Name rather than the RecodingIDs and now it seems to be working.  I think it was the deleting and re-creating that fixed it, because I've been using the RecordingIDs since last year and never had an issue until recently. However I agree with you, this makes it a lot easier to see which transactions your either using or omitting, especially if one of my colleagues goes in there they won't have to figure out what transaction recordingID XX is.  I've gone ahead and changed all my alerts to use the Transaction Name rather than the recordingIDs.

Randall