This is a feature request to evaluate solutions to the following problem.

When Zabbix Sender is told to send an item to a Zabbix Server/Proxy which does not monitor that item/host, it will reject the value. In a distributed Zabbix environment where the associated proxy server might not be known ahead of time, it's difficult (or impossible) to use Zabbix Sender to reliably send values without pre-defined lists of proxies. Methods such as live API query to obtain proxy_host for each item is time consuming and impractical.

My idea is to have some method to determine whether an item is monitored by a proxy, and if so, have zabbix_sender (or the Zabbix Server) redirect to the appropriate proxy for the host:item or respond with useful information "item not monitored by this server, try <proxy_host>". This gives coders an option to listen for an error, capture the suggested proxy_host and try again.