A user asked if it is by design that an advanced trigger set up for disk space below 10% runs only when the value of the free space changes. It was confirmed that triggers are event based, and two solutions were mentioned – restart the Monitors or add another event such as CPU utilization, which can frequently cross the threshold. CPU utilization was confirmed as the latter approach used.
Read the entire ‘Event-Based Triggers for Disk Space Monitoring’ thread below:
Hi, we configured a trigger which runs an automated action when disk space is below 10%.
The trigger seems to run only, when the value of the free space changes but it doesn’t run when it’s below 10% and stable. For example, we have some devices, which are always at 5% but the trigger does never apply.
Is this by design?
yes this is by design, our triggers are event based so the metric needs to breach the threshold to be triggered on.
Is this an advanced trigger?
Yes, it’s an advanced trigger.
@member Thanks 🙂@member You can set different trigger thresholds for different folders; this is how take into account different scenarios like this
We did this as well. Couple of ways of dealing with this.
Since the threshold needs to be breached, one way of causing that is to restart the Monitors. They will have no previous state and the trigger will fire.
One can also add another event, one that frequently crosses the threshold. @member, what was it that ‘we’ used ?
CPU utilization
Awesome! I was wanting to use that on another trigger threshold that is mostly static.
Continue reading and comment on the thread ‘Event-Based Triggers for Disk Space Monitoring’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers