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 environments from vCenter 7 and ESXi 6.
Cloudmon VMware monitoring integrates directly with vCenter and ESXi through native VMware APIs, requiring no agent installation on the hypervisor or virtual machines. Supported entity types include vCenter, Clusters, ESXi Hosts, Virtual Machines, Datastores, and Resource Pools. All discovered entities are accessible under Virtualization → VMware in the Cloudmon navigation bar.
Key capabilities include monitoring of CPU, Memory, Network, and Disk utilisation, hardware health metrics (temperature, voltage, power, fan speed, processor status) via VMware API, and continuous availability and health monitoring of all VMware resources.
VMware monitoring requires a Cloudmon probe and a VMware credential with the vSphere username and password for the vCenter or ESXi host being monitored.
| Field | Description |
| Name | A descriptive name for this VMware credential. |
| Description | A brief description of the credential's scope or the vCenter or ESXi it is used for. |
| Type | Select VMware vCenter for vCenter credentials or VMware ESXi for direct ESXi host credentials. |
| Username and Password | The vSphere username and password used to authenticate with the vCenter or ESXi host. |
| Tags | Optional labels for filtering and identifying the credential. |
| Field | Description |
| Probe | The Cloudmon probe from which the vCenter discovery will be initiated. |
| Name | A name for this vCenter discovery. |
| Hostname or IP | The hostname or IP address of the vCenter server to be discovered. |
| Port | The port of the vCenter. Defaults to 443. |
| Credential | The VMware vCenter credential created in the Prerequisites step. |
| Interval | The reporting interval at which the vCenter and its resources monitoring statistics will be pushed to the Controller. |
| Automatically Discover New Resources and Monitor | When enabled, Cloudmon automatically discovers and begins monitoring new resources added to the vCenter at each discovery interval. |
| Discovery Interval | How frequently Cloudmon scans the vCenter for new or removed resources. |
| Resources to be Discovered | The entity types to discover within the vCenter, such as Clusters, ESXi Hosts, VMs, Datastores, and Resource Pools. |
| Automatically Remove Resources No Longer Found in vCenter | When enabled, resources deleted from vCenter are automatically removed from Cloudmon monitoring after the configured retention period. Enabling this option reveals the Auto Remove Retention Period field. |
| Auto Remove Retention Period | Select how long deleted resources are retained in Cloudmon before being permanently removed. Only visible when automatic removal is enabled. |
| Alarm Rule | An alarm rule to apply to all discovered VMware resources. Optional. |
| Tags | Optional labels for this discovery. |
After the configured reporting interval, all VMware resources are discovered and become available for monitoring under Virtualization → VMware.
When discovering a vCenter or ESXi host, you can control which entity types are discovered. The Resources to be Discovered field in the discovery form lets you select specific entity types such as Clusters, ESXi Hosts, Virtual Machines, Datastores, and Resource Pools. This gives you fine-grained control over the scope of your VMware monitoring and prevents unnecessary discovery of entities you do not need to monitor.
Cloudmon simplifies navigation and troubleshooting by mapping interrelated VMware entities. ESXi hosts show their associated VMs and connected datastores. Resource Pools link back to their parent cluster. Datastores list the VMs stored within them. This mapping provides a holistic view of the virtual environment and makes it easier to monitor relationships, dependencies, and resource allocation across the VMware infrastructure.
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.
| Issue | What to check |
| Discovery completes but no entities appear | Wait for at least one full reporting interval to pass after discovery completes. Entities are not populated until the first data push from the probe. Also confirm the Resources to be Discovered field included the desired entity types. |
| Discovery fails immediately | Verify the probe can reach the vCenter or ESXi host on port 443. Confirm the VMware credential username and password are correct and that the account has read access to the vSphere environment. |
| Hardware health metrics not appearing for ESXi hosts | Hardware health data is retrieved via the VMware API. Confirm the vCenter or ESXi credential has sufficient privileges to query hardware health counters. Some hardware vendors may not expose all sensor data through the VMware API. |