In an attempt to reduce the number of tickets for our first line, I wrote a cleanup vbs which is run as a recovery task on the Logical Disk Free Space monitors. When the threshold is breached the script deletes some files/folders our first line would typically also start with.
The problem is though that the alert stays open until the next monitor interval. We do have a few mins of delay before an alert is escalated towards our ticketing system, but the delay is not big enough to simply wait till that next scheduled interval.
Is there a why I can force the monitor to recheck? Recalculating the health doesn’t do the trick. Perhaps there’s some command I can run at the end of the vbs to have the agent to re-evaluate the monitor again?