jim8424

Never mind. Easy Peasy Lemon Sqeezy. Alert Type needs to be IP SLA QoS 

I always include the alert name variable at the bottom of all alert emails. It doesn't mean anything to the recipient but it sure helped me when people start asking why they are receiving particular alerts.

Have you looked at Alert Central? We don't use it but I think it is supposed to do just about everything you are looking for.

Thanks to Shawn from SolarWinds Tech Support. We were using the 'Response Time' field instead of 'Average Response Time'. After the change, everything looks good.

My experience with Loop 1 Systems was fantastic. Excellent training experience in Austin. As cahunt mentioned, the diverse backgrounds of the class participants brought out many interesting perspectives.

Have a look at Loop 1 Systems. I've been to their training and it was fantastic. www.loop1systems.com

Thanks to everyone for the feedback. As usual, the hardest part of this process will be to get the bean counters to pony up the funds.

How about this: Trigger alert when all of the following apply Node status is equal to Down Trigger alert when any of the following apply Node Name is equal to Device01 Node Name is equal to Device02 Node Name is equal to Device03

Bump. Anyone have any ideas?

For all of my alerts with Node as the property to monitor, ${NodeName} works just fine.

Tried to order polo. Points deducted but didn't see an email to finalize order. * 03/03/2016 * Polo * 1 * 2x

I'm using ${GroupStatusRootCause} in my group status change alerts. It lists the node or nodes responsible for the group status change. It sounds kind of like what you are trying to do.

I believe your second condition group needs to be 'any' instead of 'all'. Or get rid of Status equal to Down and Unknown change it to Status not equal to Up.