Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Orion Advanced Alerting Configuration Quandry

I really like the functionality of the advanced alerting system within Orion, however, I'm running into some problems with the usability of the advanced alerting system. My company has over 1500 interfaces, nodes, and servers that we are monitoring with Basic alerts at the moment and would like to move over to Advanced alerts. So my question is a two parter:

1. Is there a way to import all currently selected monitored devices from Basic Alerts to Advanced alerts?

2. Is there a way in the advanced alert configurations to have a check-box style system to select which interfaces and nodes to monitor? The idea of having to find the corresponding NodeID for each interface and manually code that in is impossible for consideration. We also need to specify exact interfaces, so I can't specify interface types as that would improperly add all interfaces to alerting, which we need to avoid.

Any advice would be greatly appreciated. I have watched the Orion Advanced Alerting tutorial to death with no help. Thanks!

Derek Sperry

Find more posts tagged with

advanced_alerts_configuration_and_edit

Accepted answers

All comments

bleearg13

1. Is there a way to import all currently selected monitored devices from Basic Alerts to Advanced alerts?

No, unfortunately.

2. Is there a way in the advanced alert configurations to have a check-box style system to select which interfaces and nodes to monitor? The idea of having to find the corresponding NodeID for each interface and manually code that in is impossible for consideration. We also need to specify exact interfaces, so I can't specify interface types as that would improperly add all interfaces to alerting, which we need to avoid.

Again, no. Your best bet would be to add custom properties to each of your interfaces, specifying something like the type of alerting you want to do. For instance, if you have 50 serial interfaces and 200 ethernet interfaces in Orion, both consisting of internal LAN/WAN connections and customer WAN/LAN connections, you could create a custom property that differentiates between the two. Then, you can set up separate alerts for each "type" based upon that custom property.

derek.sperry

Thanks for the information. Although it certainly means a lot more work for me, we happen to be implimenting a new naming convention for our interfaces, so I'll try to make these suggested changes simultaneously.

jkennedy

How I handle it is by having my nodes grouped with custom properties that relate to their function in our network. Then I have alerts for perticular interface types on these devices and additionally exclude some interfaces based another custom property.

A note on excluding interfaces based on a custom property. If you put an alert condition like "Custom Property NOT EQUAL TO $Value". Then you should be aware the alert will not function properly if that custom property is null. An easy workaround is placing some arbitarray value in the custom property so it is not NULL.