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 custom properties differ between nodes

So I had an alert fail to fire off this weekend for a co-worker and I noticed what the problem was today: I structured the alert to use a custom volume property denoting that it is critical (1), however when I made the alert I told SolarWinds I wanted to target "Fixed Disk", and the disk was listed on the node as "FixedDisk".

Any way I can run a script to make sure all the Fixed Disk volumes are in fact in the database as "Fixed Disk"? My co-worker didn't get paged because of this silly thing and a drive filled up. I don't want that to happen in the future, the point of us monitoring our network is so that these types of things don't happen.

Find more posts tagged with

Accepted answers

dquerry

You could run a query against the volumes table.

Something like this

select * from volumes where volumetype in ('fixed disk', 'fixeddisk')

You could also change your alert to target both "Fixed Disk" and "FixedDisk"

All comments

dquerry

You could run a query against the volumes table.

Something like this

select * from volumes where volumetype in ('fixed disk', 'fixeddisk')

You could also change your alert to target both "Fixed Disk" and "FixedDisk"

mesverrum

Yeah I always write that alert with a volumetype contains 'fixed' because of the inconsistency between different vendors in how they report themselves.

mbird

Yeah, it's funny... the other disks report as FixedDisk, same node... all built from the same VM templates. It's silly, but of course this particular disk was the only one that reported differently. I think I might exclude that line entirely from the alert and focus on excluding RAM, physical memory, etc. rather than including FixedDisk specifically.