Discovery classifies the process
running on a Windows or Linux machine.
Discovering vCenter CIs
After classifying vCenter, Discovery
launches the VMware - vCenter probe, which logs into the vCenter
instance with the credentials provided and uses the vCenter API to return information about
ESXi machines, virtual machines, and resource pools. If you use a domain account to access
vCenter, specify the domain with the user name in the credential record in one of the such
The vmapp port probe can also trigger the VMWare -
CIs removed from vCenter
When a vCenter CI, such as a virtual machine, is removed, the instance marks it stale in
the CMDB, using either of these procedures:
- When Discovery runs, it creates
an audit record in the CMDB Health Result [cmdb_health_result] table for the missing CI and marks the
- If the instance is configured to collect vCenter
events, the system can also create a "stale" audit record for the CI in the
CMDB Health Result [cmdb_health_result] table from the VmRemovedEvent event, without
having to run Discovery.
Note: The Dependency View (BSM map) grays out stale CIs in its relationship diagram to
indicate that they were removed from vCenter.
You have the option of creating a CMDB remediation rule to
automatically execute a remediation workflow that can, for example, delete stale CIs. For
more information on stale CIs, see CMDB Health Metrics.