If we go to Configuration | Templates and click on Discovery next to Template VM VMware, we'll see that there's a single host prototype in the Discover VMware hypervisors LLD rule. Click on Host prototypes and then click on {#HV.NAME} in the Name column:

Here, LLD macros are used again. We looked at their use in item and trigger prototypes, but here they're used for the Host name and Visible name in the host prototype. The interesting part is the use of different macros in these fields. Host name, the one used to identify the host, isn't the hypervisor name, but its UUID. The human-friendly name goes in the Visible name field. When a hypervisor is referenced, it must be done by the UUID and it'll be referenced by that UUID in the server log messages.

The Templates tab doesn't hold many surprises; it instructs Zabbix to link any discovered hypervisors to Template VM VMware Hypervisor. Let's switch to the Groups tab now:

This is a bit more interesting. Host prototypes can instruct created hosts to be placed in existing host groups, listed in the Groups field. Additionally, they can instruct new groups to be created based on Group prototypes and created hosts to be included in those groups. Group prototypes are similar to other prototypes; the resulting names must be unique, and that means we should use some LLD macro in the group name.

The Discover VMware VMs LLD rule in this template is similar; it holds a single host prototype to be used for all discovered virtual machines. Just as with hypervisors, the UUID is used for the hostname, and that would also be the one that appears in the server log file:

In the frontend, we may search both by the Host name and Visible name. If searching by the hostname—and this might be common, as we'll see it in log files—the visible name will be shown as usual, with the hostname displayed below it and made bold to indicate that it matched the search:

In the Templates tab, we can see that the created hosts will be linked to Template VM VMware Guest. It's worth looking at the Groups tab for this host prototype. Besides adding all discovered virtual machines to an existing group, Virtual machines, two group prototypes are used here:

As seen in the hostgroup page earlier, a group would be created per hypervisor and per cluster, holding all virtual machines on that hypervisor or in that cluster.