nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Alert when local system drive usage exceeds

ppatel1

Hi Thwack Group,

I need assistance with setting up simple alert for "local system drive".

i.e. if node name "XYZ" local system used drives space exceeds 85% then send me alert by email. I do not want this rule applied to C, D and E drive.

We need generic rule so in case we add more drives for this node it will automatically monitored under this rule.

I use suppression field but it'd not working for me.

Any help will be greatly appreciated.

Thanks,

Pankaj

Find more posts tagged with

Accepted answers

nrms

They would.

A Custom Property would probably be the best way to exclude. That way you don't have to touch the alert in future - you just have a custom property called "Do Not Alert" or similar which you can set a certain value in to exclude, and then your alery would have an extra simple condition at the top level to say

"<Custom_Property_Name> is not equal to <some_value>" or alternate logic depening on exactly how you decide to configure it. The way I describe it, I'd leave the CP empty for something I do want to alert, and use a value like "No" as some_value and in the CP field for the volume.

All comments

nrms

Hi Pankaj,

What do you mean by "local system drive"? Do you mean any physical/logical drive on the machine itself, or do you mean the drive where Windows is installed?

shuth

Hi Pankaj,

I haven't had a lot of experience with Volume monitoring/alerting but I believe the following might help you. Any additional drives (F, G, etc) should trigger the alert if they go above 85%, and it should exclude the physical/virtual memory if you are monitoring those volumes on that node. I'm fairly certain the logic is correct but if anyone sees an error or has something more efficient put it up.

Additionally, be careful wth the alert suppression - the alert will be suppressed whenever it detects that condition in the database. For example, if you have a condition "Volume caption is equal to C:\" - the alert will never go off if you have a volume in the database called "C:\". It is better to include your alert logic in the trigger conditions.

nrms

OK, I think what you want to do is delete your "Trigger Alert when none of the following apply" and then all the lines that start with "Caption".

Then add a new simple condition which will be "VolumeType is equal to Fixed Disk"

(The Fixed Disk part is a drop down with all possible volume types listed. I've noticed that on my install I have Fixed Disk and FixedDisk as possible value. If you have both you will need to change the above slightly to add a new Condition Group where "any" of the following apply, and add a VolumeType is equal to" simple condition for each of the fixed disk values you have in the drop down list.)

Hopefully all that made sense!

shuth

Ah ok - I wasn't sure if something existed like that for the volume types. How would he modify the alert to exclude the C/D/E drives as I presume they would be Fixed Disk as well? He'd need an exclusion of some kind (either by volume caption or a volume custom property possibly?).

nrms

They would.