The Horizon Adapter runs on the master node or a remote collector node in vRealize Operations Manager. Adapter instances are paired with one or more broker agents to receive communications from them.
You can pair the broker agents installed in multiple pods with a single Horizon Adapter instance as long as the total number of desktops in those pods does not exceed 10,000. If you need to create multiple adapter instances, you must create each instance on a different node.
Creating more than one Horizon Adapter instance on a single master or remote collector node is not supported.
The Horizon Adapter obtains Horizon inventory information from broker agents and collects metrics and performance data from desktop agents. The adapter passes this data to vRealize Operations Manager, which analyzes the data and visualizes it on preconfigured dashboards.
In the following scenarios, create the Horizon Adapter instance on a remote collector node.
-
Large-scale installation (over 5,000 desktops)
-
To improve scalability and offload processing from cluster data nodes, create the adapter instance on a remote collector node.
-
Remote data centers
-
To minimize network traffic across WAN or other slow connections, deploy a remote collector node in each remote data center. Create an adapter instance on each remote collector node and pair each instance with the broker agent that is located in the same data center.
-
High availability (HA)
-
vRealize Operations for Horizon does not support HA. If a failover occurs, broker agents that are paired with the adapter instance on a master node cannot automatically connect to the instance on the replica node. To prevent communication interruptions, create the adapter instance on a remote collector node.
