This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Targeting interfaces and alerting on the interface

rocco_2016 over 4 years ago

I have a request to alert when any of a set of interfaces are down. I need to define this for adding additional interfaces as well.

I have created a group and added the interfaces. I have created an alert that is targeted to only the group and if any of the group members have a status of down. Which works fine when I change an interface to Down.

The issue I have found this way is that only 1 Alert is raised per "Down" status and the alert does not show which interface has the issue (tried inserting variables) and the triggered object is the Group. Which does not help when raising the alerts as ITSM tickets

This led me to create a new Interface alert, and targeted each interface. But this is not the best way when the list of interfaces grows.

Is there a better method

Thanks

Top Replies

0 d09h over 4 years ago

The behavior you are describing is normal for the 'rollup' status of groups. Using a custom property on relevant interfaces and making that a part of your logic would be beneficial. Note that the custom property could include circuit identifiers or other useful information--the kind of information that your ticket could include.
Cancel
Vote Up +1 Vote Down

Cancel
0 d09h over 4 years ago

For information on using custom properties with alerts, refer to https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Use-a-Custom-Property-in-Alerts-sw1100.htm
Cancel
Vote Up +1 Vote Down

Cancel
0 adam.beedell over 4 years ago

I think I mostly understand your question, but i'm not completely there.
I'm surprised the Members With Problems variable doesn't sort it out for you as that usually works for this type of problem.
I've had very mixed success with a workaround to translate a SQL query to an email macro, but I wouldn't recommend it. If you can write a query that would call the correct data you can use FOR XML PATH and +CHAR(9) you can force everything down to one "cell" so the macro allows it.
Cancel
Vote Up 0 Vote Down

Cancel
0 rocco_2016 over 4 years ago in reply to adam.beedell

Thanks for all the replies. I revisited this morning. Created a custom property, tagged the interfaces I needed to alert on. Created an alert that targeted only the custom property tag and created the Variable in the alert trigger action. Works perfect. Thanks
Cancel
Vote Up 0 Vote Down

Cancel