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

Alerting

Hi,

We have a 20 x SolarWinds Server environment providing visibility across a global environment, approximately 15,000 servers etc.

Is there a way where I can have a Single 'Node DOWN' alert so not multiple Node DOWN Alerts for different types of Nodes and for that single alert to push the alert out to dedicated teams such as WINTEL, Infrastructure, Virtualisation, Networks (NOC), SOC, Applications, and DBAs when one of there Nodes goes down? Or would I have have to have 7 x Node DOWN alerts, one for each of the Support Teams above?

If a Network Device went down then only the Networks Team would receive the Alert, and so on.

Is there a way using Custom Properties or Advanced Alerting to do this? For example, if I have a Custom Property (Local_Node_Owner) set against all 15,000 Nodes, can I use a single Node DOWN Alert to send the alert to that Local_Node_Owner?

Find more posts tagged with

Accepted answers

All comments

the_ben_keen

Have you looked at setting up dependencies? As an example, within my environment, I have groups set up for each of my remote sites. Within the dependencies, I have the main router for that site as the parent and then the devices below that router in a group set as the child. So if the router goes down, the devices below the router go to "Unreachable" so one alert goes out for the router is down.

I know that isn't a 100% match to what you are looking for but definitely look at the groups and dependencies. Yes, a custom property would work but this might be an easier way to go.

shuth

Typically when you want different alert actions for different devices you need a separate alert. If it's a common action like an email and you want to use a different email address, that gives you a bit of flexibility.

There are two options here:

Use a custom property that defines which department owns which device (Wintel, Networks, etc) and set up your separate node down alerts as you mentioned (so 7 separate Node Down alerts - 1 for networks that emails network DL group, 1 for Wintel that emails Wintel DL group and so on).
Use a custom property that contains the email addresses of the individual teams. E.g. "Alert_Notification_Email". Then in your single Node Down alert, in the alert trigger action that sends the email rather than putting in a static email address, input the variable for the custom property. When the alert triggers, it will send an email to whatever addresses you have in the custom property (separate multiple addresses by commas).

The second option assumes you have an email address against every device otherwise the system will send an email to " "

If you want to do fancier alerting such as "if its a network node only and still down after 30 minutes, send another email", then it will be easier to split that off into its own alert with its own trigger actions.