Agent-based monitoring for Hyper-V servers and their virtual machines. Track over 70 metrics covering CPU, memory, network, storage, availability, and VM health across your entire Hyper-V infrastructure.
Cloudmon provides comprehensive agent-based monitoring for Hyper-V environments, offering real-time visibility into the performance and health of Hyper-V servers and the virtual machines running on them. Monitoring is enabled by installing the Cloudmon agent directly on the Hyper-V server and toggling on Hyper-V monitoring in the agent settings. Once enabled, the Hyper-V server appears under Virtualization → Hyper-V Server in the Cloudmon navigation bar.
Cloudmon immediately begins tracking the performance and health metrics of the Hyper-V server and all VMs hosted on it. The server appears under Virtualization → Hyper-V Server, listed with its CPU usage, memory usage, health state, and partition count. Servers cannot be added manually from this list; the only available action is to remove a server, which happens automatically when Hyper-V monitoring is disabled on the agent.
To view a monitored Hyper-V server, navigate to Virtualization → Hyper-V Server and select the server. The detail page is organized into eight tabs: Summary, Virtual Machines, Networks, Storage, Processors, System Metrics, Outages, Alarms, and Settings.
| Tab / Section | What it shows |
| Summary | Availability, downtime, and a Virtual Machines count broken into Active and Not Monitored. CPU, Memory, and Disk usage gauges, an Alarms status panel, and a Health Timeline showing OK, Critical Failure, and Major Failure periods. Server Information lists the device name, vendor, category, IP, network, last polled time, and boot time. Hyper-V Information shows Logical Processors, Virtual Processors, and Partitions. Memory Information shows Value 1G GPA Pages, Value 2M GPA Pages, Total Pages, Deposited Pages, and Swap. |
| Virtual Machines | A list of all VMs running on the Hyper-V server, with detailed monitoring available for each VM's performance and health. |
| Networks | Network adapter and virtual switch metrics for the host. |
| Storage | Disk and storage performance metrics for the host. |
| Processors | Per-processor utilisation and configuration detail. |
| System Metrics | Time-series charts for all collected host-level metrics. |
| Outages | A history of availability outages recorded for the server. |
| Alarms | Alarm triggers and history for the server. |
| Settings | Where Hyper-V monitoring was enabled. Also where alarm triggers are added for this server. |
For each VM hosted on a Hyper-V server, Cloudmon provides in-depth performance insights:
| Section | What it shows |
| Resource Utilisation | CPU, memory, network, and storage usage for the VM. |
| Activity and Health Status | VM activity, overall health status, and performance trends over time. |
| Network Monitoring | Virtual network adapter metrics and virtual switch performance, ensuring the VM's network is operating efficiently. |
| Storage Monitoring | Disk usage and storage performance metrics for the VM. |
Alarms can be configured for individual Hyper-V servers and VMs, or at the group level for all Hyper-V entities of the same type. To configure an alarm for a specific entity, navigate to Virtualization → Hyper-V Server, select the server or VM, open its Settings tab, and click Add Trigger. Each alarm is built around a simple IF/THEN model, where you select a metric, set a threshold, and define what happens when it is breached. Learn more.
Cloudmon provides two scheduled report templates for Hyper-V: Hyper-V Monitoring (for host-level metrics) and Hyper-V VM Monitoring (for individual VM metrics). Both can be scheduled daily, weekly, or monthly and delivered automatically by email. For custom reports, navigate to Reports → Custom Report and select Hyper-V or Hyper-V VM as the entity type. Learn more.
| Issue | What to check |
| Hyper-V server not appearing under Virtualization | Confirm the Cloudmon agent is installed and reporting on the Hyper-V server. Navigate to Agents and verify the agent is active. Then confirm that Enable Hyper-V Monitoring is toggled on in the agent's Settings → Monitoring page. |
| VMs not showing under the Hyper-V server | Allow one full reporting interval after enabling Hyper-V monitoring. If VMs still do not appear, verify the Hyper-V role is active on the server and that the agent has sufficient permissions to query Hyper-V management APIs. |
| Hyper-V metrics showing as unavailable | Ensure the Cloudmon agent is running as a user with Hyper-V management access. The agent service account must have permission to access Hyper-V performance counters on the host. |
| Hyper-V metrics not collected despite the agent being active | Cloudmon uses WMI (Windows Management Instrumentation) to collect Hyper-V metrics from the host. Verify that WMIC is installed and available on the Hyper-V server by running wmic /? from a command prompt. If WMIC is not present, install it via Windows Optional Features (Control Panel → Programs → Turn Windows features on or off → Windows Management Instrumentation) or using the appropriate Windows Server feature installation command for your OS version. Once WMIC is available, restart the Cloudmon agent service and allow one polling interval for metrics to resume. |