Not everything you need to monitor is a physical box in a rack. iPM extends the same host-and-service model to virtualization platforms and cloud-hosted resources, so they show up on the same dashboards, alerts, and reports as everything else.
Virtual infrastructure (VMware)
For environments running VMware, iPM can monitor at two levels:
- The hypervisor host (ESXi) — CPU, memory, and storage utilization of the physical server running your VMs
- Individual virtual machines — resource usage per VM, and whether a VM is powered on and responsive
This typically connects through vCenter (where you're centrally managing multiple ESXi hosts) or directly to an individual ESXi host, using credentials with read-only monitoring access — a dedicated monitoring account is recommended over reusing an administrator login.
Datastore capacity is also worth watching directly, since a full datastore can affect every VM running on it at once, not just one.
Cloud-hosted resources
For instances and services running in a cloud provider (AWS, Azure, or similar), monitoring is generally API-based rather than SNMP or SSH: iPM authenticates with credentials scoped to read-only monitoring access and pulls metrics through the provider's own API, rather than reaching the instance directly over the network.
Because access is credential-based rather than network-based, make sure:
- The credentials used are scoped as narrowly as possible (read-only, monitoring-specific)
- Outbound HTTPS access from the iPM server to the cloud provider's API endpoints is allowed
Once connected, cloud and virtual resources behave like any other host in iPM — they can be grouped, filtered, added to custom dashboards, and covered by the same alerting rules as your physical infrastructure.