Alarm Configuration in Hyper-V Monitoring
Virtualization Monitoring
Alarm Configuration in Hyper-V Monitoring
Configure threshold-based alarms for Hyper-V servers and their virtual machines to detect performance and availability issues before they impact operations. Alarms can be set on individual entities or applied to groups.
Overview
Cloudmon supports alarms for all monitored Hyper-V entities including Hyper-V servers and the virtual machines running on them. When a configured threshold is breached, Cloudmon raises an alarm and can notify the relevant team members via email, SMS, or third party integrations. Alarms can be configured at the individual entity level from the entity's Settings page, or at the group level via Alarm Rules to apply consistent alerting across all Hyper-V entities of the same type.
Configuring Alarms for Individual Hyper-V Entities
- Navigate to Virtualization → Hyper-V and select the Hyper-V server or virtual machine you want to configure alarms for.
- Open the Settings page for that entity.
- Click Add Trigger to create a new alarm condition.
- Configure the trigger fields as described in the table below.
- Click Save.
| Field | Description |
| Metric | The specific metric to monitor, such as CPU usage, memory utilisation, network bandwidth, or disk space on the Hyper-V server or VM. |
| Threshold | The value the metric must breach to trigger the alarm, for example CPU usage exceeding 80% or available disk space dropping below a defined level. |
| Severity | The alarm severity level. Options are Critical, Trouble, and Attention, helping to prioritise alerts based on the impact of the issue. |
| Notify To | The users or user groups who will be notified when the alarm fires, ensuring the right team members are informed promptly. |
Configuring Alarms for Hyper-V Resource Groups
To apply an alarm rule across all Hyper-V servers or all Hyper-V VMs simultaneously, navigate to Settings → Configurations → Alarm Rules, click Add, and select the relevant entity type: Hyper-V for host-level alarms or Hyper-V VM for VM-level alarms. Add triggers for the required metrics and associate the rule with the relevant device groups. 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.
Related Articles
Hyper-V Monitoring
Virtualization Monitoring Hyper-V Monitoring 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. ...
Which versions of PowerShell support the execution of the Hyper-V installer script?
The Hyper-V installer script can be executed on PowerShell versions 5 and above.
What are the system requirements for installing Cloudmon as a Hyper-V virtual machine on a Windows operating system?
To install Cloudmon as a Hyper-V virtual machine on Windows, the following system requirements must be met: Windows Pro or Enterprise version above 10 (64-bit operating system). A 64-bit processor with Second Level Address Translation (SLAT). Minimum ...
Benefits of Agent-Based vs Agentless Monitoring
Server Monitoring Benefits of Monitoring Using an Agent Over Agentless Understand the key differences between agent-based and agentless monitoring in Cloudmon, so you can choose the right method for each device in your environment. Overview Cloudmon ...
Agent Vs Agentless Monitoring in cloudmon
Attribute Agent-based Monitoring Agentless Monitoring – SNMP, WMI, TCP, ICMP Methodology Deploy the Cloudmon Agent on each server that requires monitoring. Cloudmon uses Probes to monitor IP network endpoints and devices in the network such as ...