Vcenter and proxy per ESX cluster

[mariom]

I have vcenter (8) and few ESX clusters in differrent location. I added vcenter and vmware FQDN template. I must use zabbix proxy per each ESX cluster...I cannot change proxy/proxy group for discovered VM, and in the host prototype in discovered vm rules....Is there any way to do this - how to force change of proxy for discovered objects?

Zabbix 7.0.6 and few proxy per localization.

[cyber]

What is your aim? To use agent based templates on those discovered hosts?

[mariom]

What is your aim? To use agent based templates on those discovered hosts?

Yes, exactly. Monitoring by discovery have basic items (cpu, ram, disk etc) whithout specific application monitoring (databases, web serwers, etc..).

[cyber]

yeah... bad luck.. discovered vm-s do not get proxy choosing options..
Skip discovery of VM-s, configure autoregistration for agents, let them connect automatically to their proxies...

[mariom]

yeah... bad luck.. discovered vm-s do not get proxy choosing options..
Skip discovery of VM-s, configure autoregistration for agents, let them connect automatically to their proxies...

Thanku you cyber. I'll try another options...Proxy group on vcenter host (all proxy see vcenter), and in the agent configuration, proxy address dedicated for localization ..mayby it will work..What do you thnik about it?

[cyber]

You mean that all discovered hosts in Zabbix inherit proxy group config, but you configure only one of those proxies in agent? My logic would say, that it will not work out... Only one particular proxy is able to speak with agent, but docs say for "ServerActive": "More than one Zabbix proxy should not be specified from each Zabbix server/cluster." If that one will redirect all comms to the assigned proxy from proxy group... then it might work.. but if assigned proxy from that group is not able to speak with the agent, then there will be issues...

I have not tried proxy groups, as it does not suit our setup at all.... So I just do not know details here...

[mariom]

You mean that all discovered hosts in Zabbix inherit proxy group config, but you configure only one of those proxies in agent? My logic would say, that it will not work out... Only one particular proxy is able to speak with agent, but docs say for "ServerActive": "More than one Zabbix proxy should not be specified from each Zabbix server/cluster." If that one will redirect all comms to the assigned proxy from proxy group... then it might work.. but if assigned proxy from that group is not able to speak with the agent, then there will be issues...

I have not tried proxy groups, as it does not suit our setup at all.... So I just do not know details here...

Its works...Proxy group assigned to vcenter host, on vm installed zabbix agent and configured as active client, assinged Linux active agent template.

[cyber]

Good to know...

[mariom]

Good to know...

you were right....its not working...if proper proxy from proxy group is "assigned" by zabbix to network accessed vm its ofcoz works. Only option is create another host, add agent, assign proxy etc.. Another problem with vmware template is assigning dicsoverd vm to host group ..its also impossible.

[cyber]

Another problem with vmware template is assigning dicsoverd vm to host group ..its also impossible.

But host prototype has group selection options.. Groups and group prototypes...