Problem: After removing and subsequently re-adding any number of VMs from/to the inventory, the number of active/inactive VMs per cluster reported by the VMware Data Adapter no longer matches the number of active/inactive VMs shown in VMware Infrastructure. As a result, the Allocated vCPU/vRAM reports are also not consistent with the data shown in vCenter.
Cause: Removing a virtual machine from the inventory unregisters it from the host and vCenter Server, but does not delete it from the datastore. To be re-added, it just needs to be re-registered. To collect values against the CONF_ENTITY_ACTIVE_FLAG metric, which is used to build the SERVER_DIM_ACTIVE_VIEW metric, the VMware Data Adapter is currently using the vim.event.VmCreatedEvent event only, not the event that is triggered at re-registration (vim.event.VmRegisteredEvent) of the VMs and which reactivates them in vCenter.
Solution:
Hi Adrian, thanks for the comment and the details. I have added the missing step.
Regards,
Clemens
This is really good to have available - thanks. We have deployed and tested it today.
If this is not done, by default, the new entity DA will be a lower priority and any new events will not be reflected in the 'active entity views'.
If the datasource priority is raised above the other VMware datasources, then the changes are correctly reflected, and we see much better numbers in the VMware Platform reports J
Adrian