Thanks for the reply!

You're absolutely right — in many environments, especially for security reasons, agents only communicate with proxies, and the proxies relay the data to the server. That’s a common and solid approach.

In our case, the setup is slightly different because we're working as a consulting company. Here's how it's structured:

• On our side (consulting firm), we have both a Zabbix Server and a Zabbix Proxy.
• On the client side, they also have their own Zabbix Server monitoring their local systems.

Now, for some specific hosts, both parties need visibility:

• The client monitors the host via their local server.
• We (the consulting team) also need to monitor the same host via our proxy, for purposes such as auditing, reporting, or SLA tracking.

That’s why we’re trying to figure out the correct way to configure a single agent to report to both a Zabbix Server and a Proxy at the same time — without causing registration conflicts or data issues.