Configure a Hyper-V Host Check

Step-by-step guide to setting up the Hyper-V Host check in octoja to monitor a Hyper-V server's VMs, replicas, checkpoints, and storage.

Written By Stefan Steuer

Last updated 28 days ago

The 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 free space on the storage volumes. It is a host-level companion to the per-VM Hyper-V VM Status check.

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, the Hyper-V PowerShell module should be installed; without it the check reports virtual-machine state only.

Steps

Add the check on the Hyper-V host you want to monitor.

  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 — any of them that is not running makes the check Critical. Use VMs to ignore to leave specific machines out of the counts and alerts.
  4. Set the volume warning and volume critical thresholds (defaults 85 % and 95 %). Leave Storage volumes empty to detect the host's VM storage automatically, or list specific drives and paths.
  5. Adjust the checkpoint age warning (default 7 days) and checkpoint count warning (default 3 per VM) if needed, and keep Check Hyper-V Replica and Check integration services on for the full picture.
  6. Click Add Check.

What triggers an alert?

ConditionSeverity
The host cannot be queriedCritical
A required VM is not running, or is missing from the hostCritical
A VM is in a critical state, or a volume reaches its critical thresholdCritical
Hyper-V Replica reports a critical health stateCritical
A volume reaches its warning threshold, a checkpoint is too old or too numerous, replica health is degraded, or integration services are degradedWarning
All monitored VMs, volumes, replicas, and integration services are healthyOK

Tips

  • Install the Hyper-V PowerShell module on the host to get replica, checkpoint, and integration-service monitoring. With only WMI available, the check still reports which VMs are running.
  • 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.

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

See also: Hyper-V Host Check Reference — all fields, thresholds, and states.