Drive Space: Application Template vs Alerting

I wanted to get comments on Monitoring for Drive Space on Windows Nodes.

We currently have alerts scoped on Nodes with a Custom Property and it does work. I wanted to know if it would be better to manage this with an Application Template that could be assigned to al the nodes.

Are there benefits to creating an Application Template for this rather than just having Alerts?

Thanks!

Find more posts tagged with

drive space

Accepted answers

All comments

superfly

I'm not sure if you could do that through application monitoring other than maybe monitoring the event log? I just use the build in Volume alert to alert me on space issues.

adam.beedell

I think you'd lose auto-forecasting as a application template, but it's probably doable. Curious if you find any success if you do.

SteveK

I tend to use custom properties on either the node or volume level to handle my alerting. I have custom properties on the node for alerting, and then a custom property for critical volume action and another one for warning volume action. If you select it at the node it treats all the volumes the same (send an email, a page, console only, etc...). One of the options in the drop down is volume specific, which then ties to alerts based on the volume. This allowed us the flexability where the server team could be notified for the OS drive then an application or database team could be notified on secondary drives (without having to create unique alerts for each team).

You could potentially use a SAM to monitor volumes. I could see doing that via PowerShell script. I've played around with it in the past, and was able to get something working, but eventually scraped it.

If you have a system where drives are consistantly added/removed I could see that being a benefit. Personally I would stick with using the built in monitor volumes. That way you gather all of the various volume datapoints that SW captures natively, and it would probably be easier to manage your warning and critical thresholds.

bthorne

Alert Based

This way its identifying all the volume types FixedDisk Fixed Disk or Mount Point with your specific conditions and the % percent you require to alert.

monitoringlife

I use the native metrics vs SAM template. I do recommend you leverage the 'orion thresholds' vs a static/hard coded threshold. This will let you make overrides on a per node/volume basis without having to spin off dedicated alerts (while still rolling out a 'standard'). I also include a few custom properties to exclude the host from alerts (there are always edge cases), or to have the alert route the an alternate team in my clients ticketing system (ex: SQL volumes, or super critical/security system to bypass help desk / tier1).