VMWare Monitoring through Zabbix Proxy

[rcaugustine]

Zabbix Setup

Zabbix Server 5.2.1 on CentOS8
Zabbix Proxy 5.2.1 on CentOS8
Proxy and Server are on separate networks w/ firewall rule allowing traffic from proxy to server on ports 10050, 10051


Problem

We have a client site that is not on our network but who we are monitoring using the Zabbix proxy. So far, all of their network devices and windows/linux servers are working properly using the proxy. However, I cannot get the native VMWare monitoring to work through the proxy. I have verified that the user has proper access/permissions to vCenter. The monitoring worked when I had an on-site server (which I replaced with the proxy) so I know the configuration is technically correct. When I look at the host on the Zabbix server, I see under discovery rules an error that reads, "Couldn't resolve host name". Naturally, I replaced with vcenter dns name with the IP but the issue is still not resolved.

Has anyone accomplished monitoring VMWare through a proxy on a separate network?

[LenR]

If you're still getting "couldn't resolve", the proxy hasn't reloaded the config yet.

[rcaugustine]

Hi LenR,

Thank you for the response. I made sure that the URL is set to "https://vCenterIP/sdk" and even unlinked and relinked the template to force a refresh but I am still getting the same "couldn't resolve" error. Have you been able to monitor vCenter through a proxy before?

[rcaugustine]

After hours of beating my head against the wall trying to fix this, I realized that I fat fingered the URL macro variable name "{$URL]" instead of "{$URL}". WOW.

Issue fixed. Thank you LenR for humoring me!

[LenR]

Being over 60, the modern syntax using ({[]}) is a pain for me too ;-)