The Horizon adapter runs on a cluster node or remote collector node in vRealize Operations Manager. You can create a single Horizon adapter instance to monitor multiple Horizon pods. During broker agent configuration, you pair the broker agent with a Horizon adapter instance.
If you are monitoring multiple Horizon pods, you can pair the broker agent installed in each pod with the same Horizon adapter instance as long as the total number of desktops that the Horizon adapter instance handles does not exceed 10,000 desktops. If you need to create multiple Horizon adapter instances, you must create each adapter instance on a unique cluster node or remote collector.
Creating more than one Horizon adapter instance per cluster node or remote collector is not supported.
The Horizon adapter obtains Horizon inventory information from the broker agent and collects metrics and performance data from desktop agents. The Horizon adapter passes this data to vRealize Operations Manager for analysis and visualization where it appears preconfigured Horizon dashboards in the vRealize Operations Manager user interface.
If your Horizon environment resembles one of the following configurations, VMware recommends that you create the Horizon adapter instance on a remote collector node.
Large-scale Horizon installation with more than 5,000 desktops
To improve scalability, create the Horizon adapter instance on a remote collector node to offload processing from the vRealize Operations Manager cluster data nodes.
To minimize network traffic across WAN or other slow connections, install a remote collector node with a separate Horizon adapter instance in remote datacenters. Pair each Horizon adapter instance with the broker agent that is located in the same remote datacenter.