Bulk Changing monitored resources (Physical/Virtual/etc memory)

We're currently monitoring around 1,000 servers in Solarwinds. When the nodes were added, someone made the mistake of enabling monitoring of Physical/Virtual memory (Buffers/cached/swap for linux) as volumes.

We'd like to bulk-remove those resource monitoring selections (or otherwise find ANY way other than manually modifying each individual server's resource list).

Is there any way to do this?

The problem:

Find more posts tagged with

memory_monitor

volume_monitoring

Accepted answers

daveb7114

Kicks, Unfortunately, SW doesn't share their schema, which is one of the reasons direct deletes in SQL is kind of a last resort. Unless you are strapped for element count/licenses, I would not do the delete, but rather edit out your view objects and alerts with VolumeType = 'Fixed Disk'. Hope this helps! Dave Loop1 Systems

All comments

janene16

You can but by running SQL script.

Have your DBA run this on your Orion database:

Delete FROM [dbo].[Volumes] where caption = 'Virtual Memory' and caption = 'Physical Memory'

daveb7114

All, beware doing this as a: you may not want to stop monitoring physical RAM (virtual yes), and b: this has no where clause so it will remove ALL physical ram monitoring across all platforms. You may want to do this for LINUX but not Windows? Just mentioning because the original post didn't indicate if LINUX was their only platform. Normally you'd want to do this through settings/manage pollers/cpu and memory, but then you wouldn't get CPU either, which again, was not specified in the original post.

-DaveB7114

Loop1 Systems: SolarWinds Training and Professional Services

LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @Loop1Systems

borgan

Also, I believe that the AND will need to be an OR to get this to work.

janene16

ahh yes! thanks borgan‌

jest4kicks

Good point, Dave. We have a wide range of monitored systems, and there is a chance that such volumes exist elsewhere. (Also on the subject, we're still interested in monitoring memory statistics, but we don't want them treated as volumes.)

I checked the table that janene referenced, and perhaps the query would be even better if it utilized the VolumeType property. "Virtual Memory" and "RAM" appear to consistently refer to the type of volumes we're trying to do away with.

Now the bigger question is this; are there any dependencies or data links that are going to break by just straight-deleting the matching rows from SQL?

Thanks everyone!

daveb7114