Hello,
I consider current way of monitoring Zabbix servers and proxies to be too easy to do wrong - I mean that I too often end up with ZabbixServer data recorded into items belonging to my Zabbix proxies or vice versa, because I always forget I can't change "Monitored by proxy" on these when doing maintenance. Core of the problem is that "Zabbix server health" template will happily monitor a Proxy and "Zabbix proxy health" will happily monitor a Server. It would be nice if there was a check to prevent wrong data from being collected or at least show up as a Problem that monitoring is configured badly.

As an extension - maybe it would be also good if the template verified that the name of Zabbix component actually matches the name of Zabbix Host object? Then I would immediately notice that Host called "ProxyA" is accidentally collecting data from "ProxyB" and, consequentially, monitoring of actual "ProxyA" is broken. This will be even more important when automatic proxy selection (https://support.zabbix.com/browse/ZBXNEXT-5911) gets implemented.

I currently work this around by using the "Remote Zabbix proxy health" and "Remote Zabbix server health" templates, but that has a different usability issue: It seems {$ZABBIX.PROXY.ADDRESS} macro must be kept in sync with

manually? Also another downside is, that bypasses the encryption that is otherwise configured for the proxy.

I apologize in advance if I missed something obvious.

Cheers