Agent based monitoring for discovered VM's

[matata]

I have configured all Vcenter's to discover hypervisors, clusters and VM's which is working perfectly.

My only question is that if I would like to monitor some more in-depth items, the agent is required, but each individual VM is configured by the VM template to connect to the Vcenter, not the actual VM host name.

If I was to install the agent and configure a VM manually, do it mean that a duplicate or new host would be required?

Thanks

[matata]

I found this post from a few months ago which outlines some steps to help:

https://www.zabbix.com/forum/showpost.php?p=150173&postcount=10

Everything works well except for the hostname is in fact a uuid, which needs to be manually put into each agent config file.

Has anyone else run into the issue of not being able to properly monitor VM's outside of the Virtualcenter connection? We currently have nearly 5000 VM's, this is a pretty big problem as we need to monitor more than what can done in the current setup.

[matata]

Adding a 2nd host interface with the guests hostname or IP address does not work either, as it tries to contact the virtualcenter hostname and get access denied. Cannot change the order of the interfaces either, so not working