johnryder_cocc

I managed to get a SQL macro to work (link in my previous reply), but the alert email seems to truncate at 26 down sites. We did maintenance this weekend, and all the sites were down for a few minutes during the maintenance window, and the alert email only listed the first 26 sites out of 100. Maybe this is a question for…

Not very SQL savvy. A good analogy would be; being able to read and understand a Steven King novel, but not being able to write one. That's how I am with SQL queries.

Now I just need to figure out a way to send ONE email alert with all the down components listed, instead of 50 emails with one component each. Edit - I guess I could alert on Application instead of Component, and use some fancy SQL logic in the email from this thread: SQL variable definition to return multiple rows

Brilliant! Thanks Steve that worked like a charm.

Sorry to Necro this, but I set up an Application monitor with 100 HTTPS/HTTP monitors and used this SQL Macro; ${SQL:SELECT cast(cast([ComponentName]as varchar(max)) + '' + ' ' + '-' + ' ' as XML), cast(cast([StatusOrErrorDescription]as varchar(max)) + '' + CHAR(10) + CHAR(13) as XML) FROM…

I would like to know how to alert on high cpu by app pool, and set up actions to restart app pools that have high cpu for more than 10 minutes (run away apps).

In that alert screenshot I don't see a trigger action. What do you want the alert to do with the selected IDs after it gets them (if I'm reading that SQL select statement correctly)?

Try dumping the SWQL stuff to an email first, and see if the ${N=SwisEntity;M=ApplicationAlert.ApplicationName} starts with 'Microsoft Windows'. Depending on how Orion is passing the SWQL data to your VB script, you may just need to use the Replace that you have for sArgName2 on 0 and 1. Or it might be more complicated…

I've been puzzling over this myself, and when viewing the SWQL, it doesn't look like the scope is being applied during the SELECT, it's being applied like the trigger condition logic. This is the SWQL for a Volume low disk space alert where I set the scope for only Nodes that start with SQL and the Node Vendor is Windows…