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 not reset

hi all

one of server D drive got full and alert triggered (high volume Disk Utilization) . when i check the alert history the warning alert when triggered still not reset . how can i reset automatically when the utilization alert change from warning to critical

Find more posts tagged with

Accepted answers

All comments

adam.beedell

Click "create a special" including the condition from the above alert, or keep it on the "reset this ...when no longer true" but specify > 10% free/critical status in the trigger condition

SteveK

so if I'm reading this correctly, you do not want to see both alerts. When the alert goes to Critical you want the warning alert to clear. Personally I'm not a big fan of that approach, especially if you have time thresholds in place. If you have a system jumping between warning and critical, you would never get the alert.

You would need to update your trigger condition to be a range. So less than 20% and greater than 10%.

I do also caution going off of straight values like that. 20%/10% free on a 100GB drive is alot different than 20%/10% free on a 2TB. I recomend crafting your alerts to go off of the Warning/Critical Value Reached and/or Current value greater than Warning/Critical Value. I believe these default to 90%/95% but can be controlled on a per volume basis (Screen shots below). I believe I ran into a bug in the past were the Value Reached flag did not trip to Yes/True, so added in the Or statement of current value against Volume Warning/Critical Value. If you want the warning to clear if the critical occurs, then you would just add an additional Or block to have:

"Volume Critical Value Reached is equal to NO"
"Current Value (Percent Disk Spaced Used) is Less than Volume Critical Value".

Warning

Critical

adam.beedell

@SteveK much wisdom in this post, I have also been burned on everything you mentioned with caution in the past haha

SteveK

Yep. I never like to hardcode alert values like that if I can avoid it. There is always some unforseen system that comes around or something like SQL that wants all of the memory. So if I can set something up to a node or SAM based variable, I'm going that route instead.