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
Store

Best way to define alerts using the poller as the object

Hello all, What is the best way to prevent alerts being created for the AP when the switches reboots or goes down? We have close to 21switches and all have AP's connected. I do not want the APs to alert when the switch reboots. I tried doing this through dependencies however, you can only edit nodes. The APs do not appear as nodes in SolarWinds. Currently, we have all of our enterprise devices alerting through an alert created using the polling engine. Any node known by the engine will alert. I'm struggling defining this alert properly to achieve my goal.

Find more posts tagged with

Accepted answers

enthrall_IT

We are using Cisco 9300 access switches and Aruba APs. The AP's are picked up by the controllers but cannot be added as nodes. Below is an alert created for all of our Enterprise nodes. I added the interface description "does not start with AP". I have not tested this yet to see if this will prevent receiving alerts when the switch reboots or goes down. What do you think?

All comments

Srivan

Hello and welcome! What kind of switches and access points are you using? If Cisco, I believe APs are picked up from the controller. Do you use custom (node) properties? You can add a lot of useful information to nodes like the device type (and limit it to those devices). Can you provide any additional info... could you share the alert you are using minus anything sensitive?

enthrall_IT

adam.beedell

~'WHERE switch status = up' perhaps

Srivan

You'll have to let me know if you tested it out! Adam's suggestion of adding switch status would mean the nodes/APs only alert if the switch is still online. That would be a bit different approach than the one I would take so I'd love to hear your progress if you go that route.

If you try out the custom properties, go to All Settings > Node & Group Management.

As a comparison, I recreated the "High Response Time" alert and added a simple yes/no property for devices that excludes them from the out-of-the-box scope. I think the process would be a very similar for the APs? I hope that is helpful!

bobmarley

Possibly try this, not sure it will work. Use this query to find the numbers for the polling engines.

SELECT ServerName, IP, ServerType, EngineID FROM Orion.Engines

Then include the polling engines in the alert

designerfx

The issue with dependencies here *normally* should be groups.

Isnt' the intent to be switch -> all the AP's? If so the group should be the AP's and the dependency is switch -> (AP group) ? 1:many dependencies are a thing. Otherwise, I'd think the advanced criteria option in an alert can add an unrelated node if it's relevant.