Monitor the availability, performance, and health of all virtual machines managed by Cloudmon agents. Track CPU, memory, disk, and network metrics in real time across VMware, Hyper-V, KVM, and other hypervisor platforms.
Virtual machines share underlying physical resources with other VMs on the same host, making resource contention a common and often silent problem. A VM may appear healthy from the outside while quietly competing for CPU cycles or memory with other workloads on the same hypervisor. Cloudmon installs a lightweight agent inside the guest OS of each VM, giving IT teams direct visibility into what is actually happening at the operating system level, independent of what the hypervisor reports.
The agent collects performance data locally and stores it in an offline database for a configurable period of time. When connectivity is restored, all locally stored data is automatically uploaded and processed, ensuring no gaps in your monitoring history.
Navigate to Agents → Virtual Machines to access this view. The summary bar shows Total devices, Down, Critical, Low CPU Usage, Low Memory Usage, and Low Disk Usage counts. Distribution charts break down VMs by State, OS, Vendor, and Virtual Host, giving you a clear picture of how your virtual estate is distributed across hypervisors. The Top 5 charts highlight the VMs under the heaviest CPU, Memory, and Disk load.
The VM list shows all discovered virtual machines with the following details:
| Column | Description |
| Name | The VM hostname and the time it was last seen. |
| Agent Vendor | The virtualisation platform, for example, VMware, Inc., Amazon EC2, or Xen. |
| Boot Time | How long ago the VM was last booted. Useful for identifying VMs that have not been restarted in a long time, which can be a sign of deferred maintenance or forgotten workloads. |
| IP Info - Location | The public IP location of the VM is useful for confirming which data centre or cloud region it is running in. |
| OS | The guest operating system is running inside the VM. |
Selecting a VM opens its detail page. The overview shows key identity and status information, including the hostname, IP address, virtual host, group, customer, state, and status. It also shows availability percentage, total downtime, and current system time.
Hardware details include the processor, memory, partitions, disk, operating system, and BIOS, among other configuration information. Public IP details show the ISP, country, timezone, and organisation, helpful for confirming the hosting environment.
Lists all software installed inside the VM, showing the application name, version, publisher, and installation date. This is particularly useful for VMs running specific application workloads, allowing you to confirm which version of a service or runtime is deployed, identify outdated packages, or audit what is actually installed compared to what should be there.
Displays real-time CPU and memory usage across all running processes inside the guest OS, alongside a list of monitored system services and their current state. For virtual machines specifically, this view is most useful for:
Displays time-series charts for key performance metrics collected from inside the guest OS. For virtual machines, the most relevant metrics include CPU Utilisation, Memory Utilisation, Disk Usage, and Swap Memory, among other performance indicators. Monitoring these from inside the guest provides a different and complementary perspective to hypervisor-level metrics, helping identify cases where the VM reports high resource usage that the hypervisor does not surface.
| Symptom | Likely Cause | Fix |
| VM appears as Down | The VM may be powered off, suspended, or the agent inside the guest OS has stopped | Verify the VM is running at the hypervisor level and that the Cloudmon agent service is running inside the guest OS |
| Metrics show high usage, but the VM feels responsive | The hypervisor may be ballooning memory or throttling CPU, which the guest OS reports differently | Cross-reference with hypervisor-level metrics in the Virtualisation section to determine if the issue is at the host level |
| Gaps in metric history | The VM lost connectivity longer than the configured offline data retention window | Adjust the offline data retention window in the agent configuration |
| VM not appearing in the list | The agent may not be installed inside the guest OS | Install the Cloudmon agent inside the guest OS and ensure it can reach the probe |