Microsoft Hyper-V Host

The Microsoft Hyper-V Host check monitors the health of a Hyper-V host from the host itself — which virtual machines are running, the state of Hyper-V Replica, checkpoint age and count, integration services, and storage-volume usage. It is a host-level companion to the per-VM Hyper-V VM Status check. The check runs locally on Windows Server with the Hyper-V role or on Windows Desktop with the Hyper-V feature enabled, every 15 minutes; the interval is not user-configurable. No network credentials are required.

Checkpoints are the individual VMs' snapshots. The count is evaluated per VM; the age refers to each VM's oldest checkpoint.

Prerequisites

This check runs on the host, so set it up on the Hyper-V server's own device.

• You need the Monitoring Check Management permission. Permissions are assigned under Administration → Groups.
• An octoja agent installed on the Hyper-V host.
• The Hyper-V role enabled. For replica, checkpoint, and integration-service detail and automatic storage-volume detection, the Hyper-V PowerShell module should be installed. With only WMI available, the check reports VM state and measures storage only for the volumes or paths you list yourself under Storage volumes / paths (optional).

Steps

1. Go to Devices and open the Hyper-V host.
2. Click the Checks tab → Add Check → Microsoft Hyper-V Host.
3. (Optional) Under VMs that must run, list the virtual machines that should always be running. Use VMs to ignore to leave specific machines out of the counts and alerts. The picker offers the VMs discovered in the latest check result; you can also enter a VM name yourself, including before the first run.
4. Set Volume warning threshold (%) and Volume critical threshold (%). Leave Storage volumes / paths (optional) empty to detect the host's VM storage automatically, or list specific drives and paths.
5. Adjust Checkpoint age warning (days) and Checkpoint count warning if needed, and keep Check Hyper-V Replica and Check integration services on for the full picture.
6. Click Add Check.

After the first check interval, the result appears in the device's Checks tab.

Settings

The table lists every field in the order it appears in the check editor.

If the warning and critical volume thresholds are entered the wrong way round, the check swaps them automatically.

Exclude individual integration services

If one integration service is intentionally unavailable on a VM, leave Check integration services enabled and add an entry under Per-VM integration service exceptions. Select the affected Virtual machines or enter their exact names, then choose the Integration service. Save the check and inspect the next result. Only that service on those VMs is excluded; other integration services, VM state, replication, checkpoints and storage remain monitored. Do not use VMs to ignore for this, as that would exclude the entire VM.

Results

The overall result is the worst severity across every VM, volume, replica, and integration-service check. Failure stands apart from that roll-up: it means the check produced no result at all, and the check details name the reason.

Collected metrics

• Whether the host is reachable
• Counts of running, stopped, critical, and other VMs
• Replication job count and how many are unhealthy
• Highest checkpoint age (days) and highest volume usage (%)
• Per-VM name and state
• Per-volume root, used percentage, and free bytes
• A list of issues, each with severity and subject, plus a value, threshold, or detail where one applies

Tips

• Install the Hyper-V PowerShell module on the host to get replica, checkpoint, and integration-service monitoring and automatic volume detection.
• Long-lived checkpoints grow disk usage and slow restores — the checkpoint age and count warnings catch them before they become a problem.
• Use the Hyper-V VM Status check when you only need per-VM run state; use this Host check for the hypervisor and its storage.