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

Volume alerts

This might be a simple answer, but I'm not sure if I'm thinking this issue through properly.

I'm working on setting up alerts on a small number of servers that are all of the same platform. The alert will notify us when a certain percentage is reached on storage. so a "volume" alert. Per https://support.solarwinds.com/SuccessCenter/s/article/Create-an-alert-for-volume-space-and-usage?language=en_US I am aware that the alert needs to be built in this manner, however, I feel like the image I pasted below is incorrect.

I guess what I am having an issue with is I am unsure if the alert will apply to the listed nodes. Pretty much an issue with my IF, AND, and OR statements. I am not used to making volume alerts, and have really only needed to select the nodes I want the alert on through the checkboxes when building a "node" style alert. the "show list" option only shows volume paths, and not nodes.

Find more posts tagged with

Accepted answers

KMSigma.SWI

There's an extra layer in your selector that isn't correct. It should look something like this:

Alert "target" is a Volume

Scope of the Alert is for Nodes with Names that are Blah, Blah2, BlahIII, etc.

This is actually a painful way to do this work. Is there any other commonality amongst your node names? Do they all contain the same string? Are they all from the same Vendor? Do they have IP's that are are similar?

If you have any of those, then you've got an easier way to handle this logic.

This is actually one of the reasons that people use Custom Properties for Nodes. Then you just say "Node Custom Property" = "My Thing" as the scope.

All comments

KMSigma.SWI

There's an extra layer in your selector that isn't correct. It should look something like this:

Alert "target" is a Volume

Scope of the Alert is for Nodes with Names that are Blah, Blah2, BlahIII, etc.

If you have any of those, then you've got an easier way to handle this logic.

This is actually one of the reasons that people use Custom Properties for Nodes. Then you just say "Node Custom Property" = "My Thing" as the scope.

drattee

The nodes are all from the same vendor, and the IPs are on the same subnet based on their physical location. The customer properties for the node are generalized, i.e. these are listed as "server (IT)"

KMSigma.SWI

Well, you could go with:

Vendor = 'Whatever Vendor"
AND
IP Address starts with "10.140.27." (leaving the last octet blank for matching.)

Might be an easier filter and then if new servers come onto the network you don't need to change the logic.