We are using the built in two trigger (MB and %) logical disk free space monitor in SCOM 2012 R2. We have setup overrides for MB warning and critical for both system and non-system drives and for a group containing disks we do not want monitored. The monitor actually works fine, triggering an alert when both the MB and % free criteria are met. The problem is that it takes almost an hour for the initial alert to fire. After the initial alert, if I further fill the disk to push it from warning to critical, the alert changes within the specifiec interval, which we have left at 15 minutes. The alert also clears using the 15 minute interval.
Has anyone else seen this behavior with this monitor? A disk monitor that takes an hour to fire is not going to be very useful.