Monitoring Hyper-V

Hi everyone,

I’m currently dealing with monitoring Microsoft Hyper-V clusters. In that process I want to collect some input and insights regarding this. My goal is to find out about what we need to take care of when considering a Hyper-V monitoring solution for our Icinga Powershell Framework.

I have some questions below that can help us, but feel free to add anything else that comes to your mind.

  • How do you monitor Hyper-V Infrastructure today?
  • What exactly do you monitor regarding Hyper-V?
  • What is missing in your current solution?
  • Which findings do you expect to get from a monitoring for Hyper-V?
  • Are you able/allowed to install software on your Hyper-V hosts?
  • Do you have any other feedback or concerns?

Thank you!


Hello Blerim,

i monitor

  • ClusterStorages usage
  • VM Status (online/offline)
  • Memory usage
  • CPU Usage
  • VM Diskpace (configured disk size vs. real space used on cluster storage.
  • Configured CPUs, Memory etc.

And many more things, see my dashboard :slight_smile:

other overview:

Anf the last one is a mix of AIX/HyperV


On the Hyper-V hosts I monitor typical Windows checks (cpu, mem, disk, essential services).
For Hyper-V especially I also monitor the Cluster-shared Volumes(with the “ancient” check_wmi_volume.vbs ^^) and the age of VM checkpoints (with a self-written PowerShell script).
Also the performance counter for logical processor usage in %, because it is more reliable than the NSclients cpu check)

The VMs are monitored separately, not via the Hyper-V hosts.

In older setups I used the NSClient, in newer setups the Icinga 2 Agent.

Hi @bsheqa

At this time we reconstruct monitoring logic out Hyper-V Cluster (Failover Cluster) and stand alone host.

we monitor host, VM and cluster status
some performance count we take from Nike Eales blog

on Hyper-V host may be install monitoring and backup tools or agent