Volume Alert Trigger Condition Question

Greetings -

I am trying to setup a different volume alert using a floating point custom property for drive space. I currently have critical and full alerts setup. I was trying to work on setting up an additional alert but ran into an issue.

In the screen shot below you can see I can pull Volume > Percent used > Great Than or equal to > Volume > Custom_Property_Name.

When I try to setup a new alert I do not get the option to go Is greater than or equal to > Volume it only gives me the option for a %. I am hoping this is something simple I am missing. It has been quite some time since I setup these alerts so Things are a little rusty.

Find more posts tagged with

Custom Properties

volume alert

Accepted answers

All comments

chuckusfourus

Hi Martian_Monster,
One of our volume alerts are setup like this. Not the most efficient selection of objects but allows for us to introduce other items without modifying the alert.

This allows us to configure the same alert for a multitude of different size drives. eg 96% of 100GB is something we want to action, but 96% of 10TB is not. We configure the larger drives to have a critical of 98 or 99% allowing us to utilise the same alert for them.

Hope that makes sense?

adam.beedell

Why a floating point??

I guess you could do this in SWQL, in the drop down arrow in your screenshot you can export the current SWQL and add in the reference to your custom property but..

At the moment you're comparing a percent value, like 0-100, anything over 11% probably isnt going to trigger against a float, unless it's converted back to a number (or a percent)

If you want a custom threshold Chuck's design for using the custom threshold is fine, otherwise you could do the same with with a CP against a % custom property or a number to a number

martian_monster

This is what i am looking for. I have this configured and working in my Orion environment. I am working on setting this up with a company we acquired and I cannot get this trigger condition to show up. I have had this alert setup for quite some time and of course the notes I have on this do not mention this part.

martian_monster

It has been awhile so maybe it was not a floating point custom property. Essentially it lets me adjust per volume instead of the entire node.

martian_monster

So after you hit fixed disc you need to Add a Double Value Comparison and that allows the trigger condition that I was looking for. You had be on the right track my brain just did not put them together.

adam.beedell

Reccomend using these

But if you dont want to use those, the comparison should be the same really.