Writing monitors to target Logical or Physical Disks

<!--[if lt IE 9]>


Comments (18)
  1. Anonymous says:


    I tried to use deviceid$ instead of all instances, but the monitor would not detect any mounted disks under mouting point, wihich is driving me nuts.

    Do you have any ideas?  BTW, i'm a big fans of your blog, which helped me a lot on my daily work.



  2. Anonymous says:

    Hi Kevin,

    I have followed the same steps and have set up the threshold as 20%. I was hoping that I would be getting alerts when free space is less than 20 % but I am getting alerts only when free space is above 20%. How Can i correct that.

  3. Anonymous says:

    Hi Kevin,

    I have a Drive D: of 2 GB and i have 2 LUNS attached as D:Log and D:Data

    will i be able to monitor free space on LUNS using same process.


  4. Richard says:

    Excellent information, thank you Kevin.

  5. Ramila says:

    why some times the green satet becomes gry but it is still healthy ?

  6. John Bradshaw says:

    Saved the bacon again Kevin! Thankyou


  7. arif says:

    Thank you very much, great work kevin

  8. Gavin Speed says:

    Hi Kevin – Great blog….

    We cannot seem to get 'Physical Disk – Availability' working….

    I've turned on monitoring physical disks as described here – technet.microsoft.com/…/dd262052.aspx

    …afterwards, all we see within Health Explorer of any given server, is that for the Disk 0, 1, 2 etc only the 'Performance' element is monitored. The 'Availability' element is not checked. Can you help?


  9. Hashmi says:

    Great work Kevin, can we apply the same methodology for CPU monitoring?

  10. Ghasem Shams says:

    Hi Kevin
    Thanks for your great post.
    I Have HP-UX servers to monitor and everything is fine until we change the servers disks. when we change a disk "Logical Disk Health" monitors State goes Critical. I changed the discovery interval and no luck. what am i missing?

  11. spj11 says:

    Great post Kevin !!. I have created the monitor exactly as above. Availability is not checked in health explorer for any agent. can you please help?

  12. Robin Fleming says:

    Hi Kevin
    Thanks for your post, Keep up the good work!

  13. Sumeet says:

    Great post kevin….you saved my day….I was stuck up with this n was getting bombarded by alerts…thanks alot.

  14. Tertiaer says:

    Hi Kevin
    Thank you for very good explanation. It helped me to understand my problem.

    SQLServerRockstar asked you in 2010, how to monitor free space on LUNS or mountpoints. I have the same problem. I can see the instance, if I select my system directly. If I use "$Target/Property[Type="MicrosoftWindowsLibrary7585010!Microsoft.Windows.LogicalDevice"]/DeviceID$"
    I only get the drive and not the LUNS which are mounted to the drive. What would be the correct name for the instance?

  15. Jean Pereira says:

    Hi, Kevin!

    Very nice this post. I have a doubt…writing this way, will apply to all servers on my environment or just to a machine that I selected? My problem is… We’ve 6 VMs with OS Disk (C:) and they have others units like D: and E:, all of them are W2K12R2 running
    on Hyper-V. In SCOM, I can see all others disks of others VM normally…

  16. Kevin Holman says:

    @Jean –

    I’m sorry – I don’t understand what you are trying to accomplish. Can you explain what you want in detail?

  17. Steven says:

    how can we setup if we just needed for one drive example C:

  18. Steven says:

    some of the drive is not triggering the alerts. if we need below 20% free space. we need configure the threshold at 80.00?

Comments are closed.

Skip to main content