vCenter Web Monitoring - Couldn't resolve host name

[erasedhammer]

I have a vmware template hooked up to my vcenter host, its IP and port 443 on the main host page.
Macros:
{$VMWARE.USERNAME} [email protected]
{$VMWARE.URL} vcenter.domain.com
{$VMWARE.PASSWORD} password

But the items generated by the template keep saying "Couldn't resolve host name"
Something is wrong here since I can very CLEARLY resolve both vsphere.domain.com and vcenter.domain.com on the zabbix server itself........

[uwillc]

Please try to update your Macros to...

{$VMWARE.USERNAME} [email protected]
{$VMWARE.URL} https://vcenter.domain.com/sdk
{$VMWARE.PASSWORD} password

vSphere/ESXi URL should be written as https://IP_OR_FQDN_OF_vSphere/ESXi/sdk

[erasedhammer]

Changed the macros to:

{$VMWARE.USERNAME} [email protected]
{$VMWARE.URL} https://vcenter.domain.com/ESXi/sdk
{$VMWARE.PASSWORD} password

Still getting "Couldn't resolve host name" on the items....

[Hamardaban]

vSphere/ESXi URL should be written as https://IP_OR_FQDN_OF_vSphere_OR_ESXi/sdk
in you case - {$VMWARE.URL} https://vcenter.domain.com/sdk

[erasedhammer]

Okay, so now the macros are:

{$VMWARE.USERNAME} [email protected]
{$VMWARE.URL} https://vcenter.domain.com/sdk
{$VMWARE.PASSWORD} password

But I'm still getting "Couldn't resolve host name" on the items

[felcaetano]

Ok, so I was having the same problem with "Couldn't resolve host name" until I decided to take a look at the template's items and try to get the values manually... and for me surprise they were not using {$VMWARE.USERNAME}, {$VMWARE.URL} or {$VMWARE.PASSWORD} but rather {$USERNAME}, {$URL} and {$PASSWORD}, without the VMWARE prefix.

I don't have a lot of experience with Zabbix, I don't know if it was suppose to work regardless, but changing it finally made it work for me.

[felcaetano]

Edit: Just found out that the actual solution is to update the templates to their newest version in this repo you might want to change branches to match your Zabbix version.

[erasedhammer]

Edit: Just found out that the actual solution is to update the templates to their newest version in this repo you might want to change branches to match your Zabbix version.

Yikes, the newest template is yaml which is unsupported apparently in zabbix 5.0 lts. Apparently I upgraded by accident tho

New template appears to be working now, at least the initial items.
When triggering the discovery rules, I get
Cannot create group: invalid group name "".
Cannot link template(s) invalid token starting with "{#MULTIPATH.COUNT}".
Cannot link template(s) invalid token starting with "{#MULTIPATH.COUNT}".

It managed to create a couple discovered hosts for the hypervisors and vms. But a lot of the items under the host have the error:
Invalid update interval "{$VMWARE_INTERVAL}".