Skip to content
English
  • There are no suggestions because the search field is empty.

Monitor a standalone ESXi host (without vCenter)

What the VMware Management Pack monitors on an ESXi host that is added directly as a connection, and which data only vCenter provides.

Applies to: Opslogix VMware Management Pack 26.11.4549.0 and later · SCOM 2019, 2022, 2025 · ESXi 7.0, 8.0, 9.0
Last updated: November 2026 · Reading time: 4 minutes

You can add an ESXi host that isn't managed by vCenter as its own connection, the same way you add a vCenter server. This article explains what the VMware Management Pack monitors on such a standalone host, and which data only vCenter can provide.

Use version 26.11.4549.0 or later. In earlier versions, such as 26.10.4540.0, the discovery of a standalone ESXi host can fail on every run with Unable to authenticate with REST api. The host, its datastores and virtual machines are then not discovered or updated, and no override works around it. See Discovery fails with "Unable to authenticate with REST api".

Add the host

  1. Create a monitoring account on the ESXi host itself, with the same permissions as a vCenter monitoring account. See What permissions are needed in vCenter / ESXi?
  2. Add the connection in VMware MP Configuration. In Name, enter the FQDN or IP address of the ESXi host. See Add a vCenter or ESXi connection.
  3. Assign a license to the host, as for the hosts of a vCenter. See Assign VMware MP licenses to ESXi hosts.

Discovery runs in stages: first the connection and its datacenter, then the host and datastores, then the virtual machines. It can take several hours before everything is discovered. See How long does VMware discovery take?

What is monitored

AreaOn a standalone ESXi host
Host, datastores and virtual machinesDiscovered and monitored, including the ESXi host state monitors and the virtual machine monitors.
Host and virtual machine performanceCollected. ESXi provides real-time statistics for hosts, virtual machines and resource pools.
RAM disksThe VMware ESX Host Ramdisk % free and KB free space monitor and the VMware Get Host Ram Disks task read the RAM disks from the host itself.

What only vCenter provides

Some data comes from vCenter, not from the ESXi host. On a standalone host, the management pack skips it without errors:

  • vSphere tags. Tags are stored in vCenter. The Tags property of the host and its virtual machines stays empty.
  • Datastore performance. ESXi has no performance statistics for datastores; vCenter collects them. The datastore performance rules return no data. Datastore space is still monitored.
  • Clusters. A standalone host has no cluster, so there are no cluster objects, and the cluster monitors, performance rules and vSAN cluster monitoring don't apply.
  • vCenter Server Appliance monitoring. There is no appliance. The VMware Appliance Monitoring management pack doesn't discover anything for an ESXi connection.

If the host is also managed by a vCenter that you monitor, add the vCenter instead. You then get the vCenter data as well, and the host isn't monitored twice.

Verify it worked

  • In the Monitoring workspace, the host, its datastores and its virtual machines appear in the VMware views after discovery.
  • The Operations Manager event log on the management servers of the VMware resource pool shows no Unable to authenticate with REST api warnings for the host.

See also