I would like to suggest an improvement on the Vmware template: Currently the creation of "Hypervisor" and "VMs" object is based on the direct name fetched from the API, it can lead to problem if you have VM with the same name in different ESX (ex: in case you have a "continuity plan" or just similar applications in different ESX), the Hostname & visible name should probably make reference to the parent ESX to allow creation of the host, else it fail with "xxx already exist" as per the unicity rule of hostname for Zabbix :)
That's a quick fix but I though it would be interesting.
Hello Zabbix team,
I would like to suggest an improvement on the Vmware template: Currently the creation of "Hypervisor" and "VMs" object is based on the direct name fetched from the API, it can lead to problem if you have VM with the same name in different ESX (ex: in case you have a "continuity plan" or just similar applications in different ESX), the Hostname & visible name should probably make reference to the parent ESX to allow creation of the host, else it fail with "xxx already exist" as per the unicity rule of hostname for Zabbix :)
That's a quick fix but I though it would be interesting.
Regards