Set individual volume thresholds for easier diskspace monitoring

This was implemented in SAM 6.2.

Hi

Can you send me a link to the details of the SAM 6.2 implementation.

I monitor both windows and linux servers. Will this work for both?

I got that far but can not see how to alert on Critical. Do I have to add not equal to all the above statements to capture Crit?

Only values that exist currently are shown in the drop down. You can type "Critical" into the field manually if you have no volumes that are currently critical.

Its not allowing me to type; just allows a drop down. I have many critical too.

Hmm.. I see what you mean. I've logged this as a bug which is being tracked internally under CORE-1070. Please open a support case so we can provide you with a fix as soon as it's available.

Thanks! I opened a ticket.

Thanks! I opened a ticket.

I have the same issue. Let me know what the fix is.

Sent from my iPhone

If you choose to alert on Volume Capacity Forecasting instead of just Volumes you can then choose to alert against a Volume's Critical Threshold (and yes, the Current Value and Critical Threshold in the Volume Capacity Forecasting is the actual percentage used and Critical Threshold of the volume and not the Forecast thresholds.  The Forecast thresholds and usage are available in the drop-down as well, but the Current Value and Critical Threshold are for current usage, not forecasting).  See below:

My biggest problem with the new Volume thresholds, and the reason I still use Custom Properties to do my thresholding (is that a word?  Spell-check doesn't think it is, but oh well.), is that there is no easy way to bulk edit multiple volumes' thresholds at a time.  Say you have 500 Windows servers in Orion and you want to set a different Critical Threshold for all of the C:\ drives.  Since in Manage Nodes you can't choose Volumes like you can Interfaces, there is no way to easily select all of the C:\ drives.  You would have to individually expand each and every Windows node and manually click their C:\ drive, then click Edit Properties and set them.  This is extremely tedious.

They really need to just make the Manage Nodes screen act like the Custom Property Editor but also add the ability to "Group By" Node System/Custom Properties as well as "Group By" the Object's System/Custom Properties.  For instance, if you are editing Interfaces you should have the choice to "Group By" all Node System/Custom Properties and all Interface System/Custom Properties.  The current Manage Nodes screen is infuriating when editing Interfaces since you can't "Group By" Interface Properties and the current Custom Property Editor is infuriating when editing Interface/Volume/Applications since you can't "Group By" Node properties...  I can't imagine it would take the SolarWinds Developers long to add this functionality.  The code already kind of exists since you can already "Group By" Node Properties in the Manage Nodes screen when editing Interfaces (as I've already stated) and you can already "Group By" Interface/Volumes/Applications properties when editing Interfaces/Volumes/Applications in the Custom Property Editor (as I've also already stated).

But I digress, just adding a Volumes drop-down to the Manage Nodes screen would be a good start and actually make the new individual Volume Thresholds useful.  Also, we need Space Thresholds as well as Percentage thresholds for Volumes.  For very large volumes being able to set an Available Space threshold would be a lot more useful than a percentage threshold.  Many customers ask me for this and I have to create Custom Properties to allow this functionality still.

I thought this would be the right answer for me but although the alert was working properly our Triggered actions (emails to the support team) could not grab variables from the custom properties on the parent node to the volume.

I ended up creating new custom properties on Volumes to use for the threshold number.

I then was able to alert off of Volume instead of the Volume Capacity Forecasting.  Alerting off of Volume allowed the triggered action to be able to grab those vairables from the parent node.

So how did you setup the custom property?  Did you setup 3 different ones?  I have used custom properties for a few basic things in reports and dashboards but this one looks a bit more advanced for me. 

Under the "Main Settings & Administration" page, "Node & Group Management" section, you "Manage Custom Properties."  I added the customer properties, and the key for using it in these alerts was to make sure it was for Object Type "Volume" and the Format to "Floating Point Number."