VMWare Collector - Maps that Can Dynamically Update VM Hosts

[funwithzabbix]

Is there a way to have a map dynamically / automatically update with the VMs that are assigned to a specific host (or host group)? I created a map with 2 host groups, but I could not figure out how to make the VMs automagically appear. As vMotion will move VMs from one host to another, I thought it would be cool to have a map that shows graphically what VMs are running on a specific host. This might be too sophisticated to ask Zabbix to provide in a basic out of the box configuration, but I figured I would ask and confirm.

[Hamardaban]

Try to do this: using LLD vmware.hv.discovery create hosts (from host prototype) for detected VMs. https://www.zabbix.com/documentation...scovery_fields
Then put them in a certain group of hosts. https://www.zabbix.com/documentation...evel_discovery
Place host_group_element on the map. https://www.zabbix.com/documentation...ps/host_groups

[funwithzabbix]

Thanks! I am using the template "Template VM VMWare", with a Collector that goes to vCenter and pulls in Hypervisors (VMWare Hypervisor Template), VMs (VMWare Guest Template), etc. Unfortunately the way VMWare is behaving, the call to vCenter creates Discovery host groups as follows: Datacenter, Datacenter (vm)....Cluster, Cluster (vm). Because there is no host group for a specific host, there is no way to see at a moment's notice, which VM is on which particular host. But, your help DID allow me to put a map of the Datacenter (which has hypervisors in it), and then insert a link to the VMs. Which isn't half bad at all.

Another issue I am having (which maybe I need to make a separate post about), is that all of the IPs on all of the hypervisors and VMs in Zabbix, are 127.0.0.1. VMWare Discovery likes to name the hosts {HOST.HOST} with a long uuid that means nothing to the end user, but I guess allows vCenter to correlate the object. So I have had to change the templates to show the {HOST.NAME} on problems so people don't have to log in and decipher the uuid. This helps tremendously on the maps, also, to use {HOST.NAME}. But I would like to figure out, or understand, why all of the IPs come in as localhost 127.0.0.1.