Alert Trigger Logic

I believe your logic catches D: due to Node being true AND Fixed Disk less than 35%
The C: captions being true also allow the D: Fixed Disk to be processed.

When we were presented with monitoring servers with drives needing different thresholds, we set up monitors as described below.

From the manage Nodes page, we edited the threshold for each drive we wanted to monitor.

We set up the scope in much the same way you did, and then triggered on Volume Capacity Forecasting.

Maybe something similar will benefit you.

nathatnwilson@bloominbrands.com​ is correct about the logic;  when you nest a condition it places parenthesis around that nested portion

So overall your argument is;

Volume Caption = C label1 or Volume Caption = C label2 or Volume Caption = C label3 or (Volume % Avail <= 35 and VolType = Fixed Disk)

rearrange your argument visually - AND at the top with Vol% and Type, then OR Nested with the 3 captions; but if you want to go one further use a custom property on either the node or volume (wherever works best, or possibly holds the needed granularity detail) and use the CP instead of matching the caption.

- If CP on volume just match the value of the custom property (it will not matter if other volumes do not have a value - but it will be open if you need to use more values later on)

- If CP on Node, match value to node in the SCOPE - then use begins with to match the volumes (since all C), or another volume custom property to keep things dynamic.

If you use CP values, as the entities change - node or volume refreshed or RMA'ed you simply set the CP values to make the 'new' replacement entity fall within the alert scope instead of having to edit the alert to exactly match the hardware you are currently monitoring - and preventing alert re-trigger.

-CharlesH

Loop1 Systems: SolarWinds Training and Professional Services

• LinkedIN: Loop1 Systems
• Facebook: Loop1 Systems
• Twitter: @Loop1Systems

Thanks.  I will give is a try.

The easiest method here is to use the power of Custom Properties. This way you can create a single alert which applies to ANY Volume.

If you create a Volume Custom Property which has the required threshold (ie C: = 35 / D = 10) and then you create a single alert that triggers if the current capacity is Less than or Equal to the custom property value.

Example:

Regards

David

Hi David. 

I just came across this method and for me, this will be what I move forward with.  It was sorta of an 'ah-ha' moment and realized I wasn't leveraging the properties for alerting effectively.  Thanks for opening my eyes. 

For those that do not following:

You create a custom property that will add a field on your node, ie "Custom Threshold D drive", via the settings page. 

Navigate to the node and view the Properties of that node.  Add whatever value you want to alert on on for that drive.

Create the alert with the trigger condition like David's suggestion above.  Mine is below. 

You can then use the CustomProperties variable to populate a notification or action. 

Thanks cha-chang! just one important thing to remember - Make sure you create the Custom Property on the VOLUME, not the Node, as they work differently