Jan-Otto Kröpke
d819362150
Every optional collector of the mixin now has alerts, generated only with that collector enabled in _config.collectors: clock source, disk drive status, page file usage, license status, scheduled task results, pending updates, Hyper-V WMI and replication health, failover cluster nodes, resources, groups and shared volumes, Storage Spaces pool and virtual disk health, DHCP scope exhaustion and DNS zone transfer failures. The alerts of the pagefile, diskdrive and license collectors join the memory, disk and system groups; the other collectors get a group of their own. New knobs: taskSelector, sharedVolumeSelector, pagefileUsageThreshold, dhcpScopeFreeWarningThreshold, dhcpScopeFreeCriticalThreshold and updatePendingDuration. The test configuration enables every optional collector and tests/optional.test.yaml covers the new alerts. Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
1.7 KiB
title
| title |
|---|
| WindowsHyperVWMIUnhealthy |
Meaning
The Hyper-V WMI namespace root/virtualization/v2 on the host has not
answered a minimal query for ten minutes. The alert needs the hyperv
collector with its wmi_health subcollector. While the namespace is broken,
the virtual machine, replication and virtual hard disk metrics that come from
WMI are missing, so the other Hyper-V alerts cannot fire.
Impact
Management tools such as Hyper-V Manager, Failover Cluster Manager and System Center cannot manage the virtual machines on the host. Backups that use the Hyper-V VSS writer fail. The virtual machines themselves usually keep running.
Diagnosis
-
Inspect
windows_hyperv_wmi_healthandwindows_exporter_collector_success{collector="hyperv"}for the host. -
On the host, test the namespace and the management service:
Get-CimInstance -Namespace root/virtualization/v2 -ClassName Msvm_ComputerSystem | Select-Object -First 1 Get-Service vmms, vmcompute, winmgmt winmgmt /verifyrepository -
Check the System and the Microsoft-Windows-Hyper-V-VMMS logs for errors of the Virtual Machine Management service, and the WMI-Activity log for provider failures. A stuck
vmmsprocess or a corrupt WMI repository are the usual causes.
Mitigation
Restart the Virtual Machine Management service with Restart-Service vmms;
running virtual machines are not affected. If the repository is inconsistent,
run winmgmt /salvagerepository, and register the Hyper-V provider again with
mofcomp of the Hyper-V MOF files only when Microsoft support advises it. Plan a
restart of the host if the service cannot be recovered. Confirm the health
metric returns to 1 and the Hyper-V metrics appear again.