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

Monitoring Volumes (Resources)

While I can see there is a report which will list what volumes (resources) are being monitored, I cannot find one which will show you what volumes in total are available.

The setup (I'm not sure if this is default or not) is for Solarwinds to put a checkmark next to all the resources it sees at the time a node was entered into the database. It will not (at least our environment) monitor any new drives/volumes added at a later date.

So, for example, Node Y is entered into Solarwinds and it automatically begins to monitor C:\ .. .later another volume is added (D:\ for eample).

Solarwinds does not automatically begin to monitor this new \ volume.

Either:
A) is there a way to tell Solarwinds to monitor ALL volumes
(I figure I can set the alerts to only be concerned with 'fixed disks' to avoid any conflict with potential floppy/CD/etc drives)
run a report to show what volumes are currently monitored (I have this) as well as a report to show what volumes are available to monitor

B would be my preferred choice as I can then look through and figure out which are/aren't and configure manually from there.

Find more posts tagged with

Accepted answers

All comments

hpstech

There are so many threads on this issue. Its one of the most painful pain-points of the product.

Most people new to the product only learn of this when they get burned by a missed disk alert. We did 8 years ago. And ever since then, its been a bummer to manage.

No, discoveries is not the answer.

jklundy

Curious why you say discoveries is not the answer? It works for us. Just wondering if it's causing a problem that I am not aware of.

I divide our network into ~ 1/7 pieces based on IP ranges and scan each segment 1x week.

chucksimalchik

This is what I do. My pain point is that I can't get a report of "New Volumes Discovered". If I go to the Scheduled Discovery Results I can see nodes that have volumes marked as new, but I'm currently fighting with a SWQL query that'll get me a neat and tidy report of those.

In lieu of that, someone on my team pages through the report to find new volumes and adds them (we don't add things automatically, for a number of reasons). I am so close (I think) to a query that'll give me what I want but I can't seem to get all the way, and "real" work inevitably gets in the way whenever I get back to revisiting it.

hpstech

There you go, this is the pain.

When you have 3000+ servers, and 50+ different windows credentials cycling though those 3000+ servers, this is a horrific nightmare, blasting 3000 servers looking for a volume your admin in Brussels added last week without telling you.

Its sloppy and and imperfect. What is the solution? Not sure....but the many threads with this issue leads to the conclusion that its a valid pain point and its definitely not ideal to blast thousands of servers looking for a volume.