Alarm Configuration in VMware Monitoring
Virtualization Monitoring
Alarm Configuration in VMware Monitoring
Configure threshold-based alerts across all VMware entity types to detect performance and availability issues proactively. Alarms can be set at the individual entity level or applied to groups of VMware resources.
Overview
Cloudmon supports alarms for all monitored VMware entities including vCenters, ESXi hosts, clusters, virtual machines, datastores, and resource pools. 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 entities of the same type.
Configuring Alarms for Individual VMware Entities
- Navigate to Virtualization → VMware and select the entity type (ESXi Hosts, Virtual Machines, Datastores, etc.).
- Click on the specific entity 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. |
| 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 VMware Resource Groups
To apply an alarm rule across all entities of a specific VMware type simultaneously, navigate to Settings → Configurations → Alarm Rules, click Add, and select the relevant VMware entity type such as VMware ESXi, VMware VM, or VMware Datastore. 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
VMware vCenter / ESXi Monitoring
Virtualization Monitoring VMware vCenter / ESXi Monitoring Monitor your entire VMware infrastructure from a single page. Covers the vCenter environment summary, ESXi host health, cluster resource usage, virtual machine performance, datastore storage, ...
Is VMware credential with read access enough for monitoring Vcenter?
Yes, as we are fetching the VMware through Native API's read access is enough for monitoring
Is it possible to monitor VMware ESXi?
Yes, ESXi residing in a vCenter will be discovered and monitored or else a standalone ESXi could also be discovered and monitored., refer VMware monitoring for more details.
When is an alarm triggered in cloudmon?
An alarm is triggered based on the configuration of the corresponding alarm rule when an IP endpoint or device exceeds the threshold value that has been set. In other words, when the monitored metric goes beyond the defined limit, the alarm will be ...
VMware Monitoring
Virtualization Monitoring VMware Monitoring Agentless monitoring for VMware infrastructure using native vCenter and ESXi APIs. Supports over 200 metrics across clusters, ESXi hosts, virtual machines, datastores, and resource pools. Supports VMware ...