VMware vSphere
The VMware integration reads vCenter Server, or a standalone ESXi host, through the vSphere API. It runs on an Integrator inside your network.
It is read-only. The integration never powers, migrates, snapshots or reconfigures anything.
What it collects
| Sync | Collects |
|---|---|
| Hypervisor discovery | Datacenters and clusters, and every ESXi host with its version, build, hardware, CPU, memory, connection state and management addresses |
| Virtual machine discovery | Virtual machines with their guest OS, addresses, MACs, CPU, memory, power state, tools status and host; templates |
| Network discovery | Port groups, and distributed port groups with their switch and VLAN |
ESXi version and build are reported so outdated hypervisors are visible. Hosts and virtual machines are kept as their own records, alongside hosts rather than written into them; one whose address matches a host a scan has found is linked to it.
Create a read-only account
- In vCenter, create a user (for example
[email protected]). - Under Administration > Access Control > Global Permissions, grant it the built-in Read-only role and select Propagate to children.
For a standalone ESXi host, create a local user with the Read-only role on the host.
Connect it
- Under Integrations, add VMware vSphere with the vCenter (or ESXi) hostname and the account's username and password.
- In the integration's settings, assign the Integrator that can reach vCenter.
- Enable the syncs you want.
vCenter ships with a certificate from its own VMCA. Unless that CA is trusted by the Integrator host, the first connection records the certificate's fingerprint and later connections must present the same certificate. After replacing the certificate, clear the pinned fingerprint in the integration's settings.