Currently, a Zabbix proxy can belong to only one proxy group, and a host can be monitored by only one proxy group.

This limits high-availability deployments where proxies are distributed across multiple independent datacenters, providers, or countries.

For example:

• Germany proxy group: proxy-de-01, proxy-de-02
• Ukraine proxy group: proxy-ua-01, proxy-ua-02
• Europe proxy group: proxy-eu-01, proxy-eu-02

Hosts normally should be monitored by their local proxy group. However, if all proxies in that group become unavailable due to a datacenter, provider, or routing outage, proxies from another group should be able to take over automatically.

Currently this requires putting all proxies into one global proxy group, which removes the logical separation between sites.

Possible solutions:

1. Allow a proxy to belong to multiple proxy groups.
2. Support hierarchical/nested proxy groups, where a parent/global group can provide fallback proxies for child groups.
3. Allow a host to have multiple proxy groups with priorities, for example:
   • Primary: Germany
   • Secondary: Europe
   • Fallback: Global

Expected behavior:

As long as the primary proxy group has available proxies, the host should remain assigned to that group. If the entire group becomes unavailable, Zabbix Server should automatically move the host to the next configured proxy group. When the primary group becomes healthy again, Zabbix could optionally move the host back.

This would provide datacenter-level and provider-level failover while preserving local proxy groups and load balancing within each group.

In our environment, proxies are deployed in several independent hosting providers and countries. Each location has two proxies for local HA. A failure of the entire provider/location currently cannot be handled by another proxy group automatically.