nodes monitored through zabbix proxy are showing offline

[mbannout]

Hello,
I have a zabbix server setup in location A which is successfully monitoring nodes in Location A and Location B.

I installed a Zabbix proxy in Location B and configured it as active, i also configured it on the Zabbix server in location A. the proxy on the frontend shows the version and "last seen (age)" is always less than 5 seconds.

when i configured one of the nodes on the frontend to be monitored by the proxy, the node is not seen anymore, the latest data is old. when i revert back to direct monitoring, the nodes is seen again and monitored properly.

Interface of the node on the frontend is still configured with the node IP, i also have not configured Zabbix proxy on the node zabbit-agent configuration file because none of the guides mentioned that this is required.

Zabbix server version = 6.4.8
Zabbix proxy version = 6.4.8
Zabbix agent running on the node = 6.0

appreciate any help to fix this problem.

[cyber]

Of course you need to change Server and ServerActive settings in agents config. How else would that agent know, where to ask for active checks or whom to allow to query of passive checks?

To say, that no page instructs to change it in agents config is a lack of reading.. Config parameter definitions all say "server or proxy name" (https://www.zabbix.com/documentation..._agentd#server)... if proxy acts on behalf of server (https://www.zabbix.com/documentation...concepts/proxy) and agent parameter defines access for that server/proxy.. Its like putting 1+1 together...

[mbannout]

thanks for the reply.
It is not lack of reading, I know the parameter definitions in the zabbix-agent config files and that's why I mentioned that I have not made changes to it.
to me putting 1+1 together would have been to propagate changing the "monitored by" on the frontend to the agents in the remote location and changing the config files automatically, but that's just me.
I have around 75 nodes in location B and I didn't want to think about changing the config on that many nodes.

Anyway, thanks again for the reply i'm gonna bite the bullet and go ahead with editing the agent config files.

[cyber]

Well, server is not able to change any (config) files on hosts or push anything there. Which is good for security.
You would have to make sure at first, that all the connections exist etc.. Having many hosts to maintain calls for some automation, ansible or something...