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

Volumes Advanced Alerts

Our server team has finally come round to the idea that using alerts on NPM is worth doing. So I've been given the task of setting these up.

I have a couple of questions.

1. They want an alert to trigger when the disk space goes below a certain level, in the trigger condition and I set it up to alert when any given volume goes below say 5gig can I just put in 5 or does it need to be the bytes equivalent so 5368709120?

2. If I just allow the above to trigger for any volume, given in volume view it includes physical and virtual memory will these also trigger on a general volume alert?

Thanks

Jon

Find more posts tagged with

Accepted answers

mcbridea

That is a good approach to qualifying only the volumes of interest. The vol numbers are in bytes if you decide to use absolute numbers.

All comments

Congo

What I do is label the volumes that I want to monitor (so that I dont monitor /tmp and other always full volumes) with a custom property.

I then create two different alerts to fire at 85% and 90% usage, where my custom property is also in place. The 85% is the warning shot, and the 90% is considered critical. That way I can monitor my 1110 volumes with just two alerts, and it works perfect for our environment. You should be able to set up similar alerts for low end thresholds instead of high.

mcbridea

That is a good approach to qualifying only the volumes of interest. The vol numbers are in bytes if you decide to use absolute numbers.

robertcbrowning

We've also added 2 custom property fields to identify the percentage full that constitues warning or critical levels. We populate them with defaults, but then adjust the custom property so that we can specify different criteria per volume.