Alert Automation for Drive Space

martian_monster

Greetings -

Another Alert Automation Question. I am trying to setup an alert automation to assign 95% utilized to all of my production Windows nodes.  I put together a query to try and break down just the prod Windows nodes and wanted to see if there is a better way to do this.  We kind of have a naming convention and have been working on that the best I can.  

With this below I am grabbing only Prod Windows nodes.  

This is the trigger - 

I have these configured to write to NetPerfMon so I can run a report on this daily on what nodes were assigned drive space utilization.   

Just looking for suggestions or adjustments I can make on these.  Thanks! -Dave

chad.every

There are multiple ways to do it, not a single right answer, so it might boil down to what works best for you. This is what i've done in the past.

Part 1: use a little known alert variable called 'Warning Value Reached' and 'Critical Value Reached'. These follow the entity thresholds defined for that node/interface/volume. So you don't have to create custom properties to define a threshold, simply reference what is already in the tool. It also allows you to change the entity thresholds individually and still use the same alert and not have to split it into multiple alerts.

 Modify Alerts To Be Smarter With Node Thresholds 

Part 2: Using the alert engine for automation. This is also a lesser known item since most people only consider the Alert engine for, well, alerts. However, some of the alert actions allow you to set custom properties. You could create a node and/or volume custom property with something like 'IsProduction' with a Yes/No or 'NodeClassification' with a drop down of Prod, Dev, or Test.

Since you have several conditions already defined, it's partly there. Then when new entities are added in the future, it'll auto tag them with the correct custom property. You might end up creating a handful of automation alerts. Caveat is the Alert Trigger Condition entity dropdown has to match the custom property type.

e.g. Trigger Condition Alert on 'Node' --> Alert Action Change Custom Property for Node. 

e.g. Trigger Condition Alert on 'Volume' --> Alert Action Change Custom Property for Volume. 

 Alert Engine Automation - Automatic Custom Property Assignment 

Part 3: The volume alert trigger condition would then be simplified to Node Custom Property = ABC and Volume Custom Property = XYZ and Warning/Critical Value Reached = true.