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

Create hardware alerts based on group membership

Hello,

I'm still an Orion newb, so hopefully someone can help me out.

I have several nodes under a group. I want to have email alerts be generated for anytime there is a critical hardware failure for these nodes that fall under the group. Right now when I go into the Alert Manager and attempt to create an alert, I'm unable to find a way to break it down to only look at hardware failures for a certain group.

Can someone help me out?

Find more posts tagged with

Accepted answers

aLTeReGo

I would recommend using Custom Properties to achieve the kind of alerting you're looking for.Groups are for dependency mapping and root-cause analysis. Instead of using groups you should look at custom properties, which are far more powerful and were designed specifically to achieve what you're looking to accomplish. This user created video below should help get you started.

SolarWinds Custom Property (Grouping) and Alert. - YouTube

All comments

superfly

This thread discusses a couple of different options for you. Hopefully one will suit.

http://thwack.solarwinds.com/thread/53600

aLTeReGo

SolarWinds Custom Property (Grouping) and Alert. - YouTube

vpbcarder

Thank you to you to both!

I have another question - I'm having an issue setting up my email alerts for this. I would like the alert to tell me which piece of hardware component failed. It doesn't seem to be working.

Email comes over looking like this:

aLTeReGo

I suggest copying and reusing the "Alert me when any hardware component goes into a warning or critical state" alert that comes out of the box and customizing it to suite your needs. It already does exactly what you're looking for minus the account limitations. Alternatively you can use the macros ${SensorsWithProblems} or ${SensorsWithStatus} to include information about which hardware components are in a failed or degraded state.

vpbcarder

Can we mix "type of property to monitor" - the last time I tried switching that, it changed the whole alert to fit that property, if that makes sense. Right now my alert is under "Hardware" - where the one you're talking about is APM: Hardware Sensor.

I didn't think it was using an APM component to monitor hardware, I thought that was more of a WMI thing? (I could be completely wrong).