Horizon Remote Cluster/Pod Health Test
In a cluster pod or multi-pod Horizon environment, the use of local and remote Horizon connection servers ensures high availability, scalability, and efficient management of user sessions across multiple locations.
A Remote Horizon Connection Server is often located in a different pod or remote data center. In a multi-pod deployment, remote connection servers facilitate connections to Horizon infrastructure in different geographical locations or environments. Remote Connection Servers are used when users are connecting from a different pod, either for disaster recovery, load balancing, or geographical proximity reasons. The Remote Horizon Connection Server brokers user connections to the Horizon resources (virtual desktops or applications) in another pod.
An endpoint on a Horizon Connection Server typically refers to the network address (e.g., IP address or Fully Qualified Domain Name, FQDN) and port through which the Horizon Client connects to the server. This endpoint allows the Horizon Client or a web browser to reach and establish a connection to the virtual desktop or application session.
If the endpoint on a remote Horizon Connection Server is not enabled or is offline, then, during disaster recovery, users may not be able to establish connection to the virtual desktop or application session. This is why, it is essential to monitor the status of the endpoint on a remote Horizon Connection server. The Horizon Remote Cluster/Pod Health test helps administrators in this regard!
For each remote Omnissa Horizon Connection Server configured on the target Omnissa Horizon Cluster/Pod, this test helps administrators identify whether/not the endpoint is enabled and the current status of the endpoint. Further, this test reveals the remote Omnissa Horizon Connection Server with the maximum response time.
Target of the test : An Omnissa Horizon Cluster/Pod
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each Omnissa Horizon Connection Server configured on the Omnissa Horizon Cluster/Pod being monitored
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
Refers to the port used by the target Omnissa Horizon Cluster/Pod. By default, this is set to NULL. |
Connection Server Name |
By default, this test connects to every Horizon Connection Server configured in the Omnissa Horizon Cluster/Pod remotely and collects the required metrics. For this, it is necessary to specify valid credentials of the Horizon Connection Servers. To help administrators provide these credentials quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the encircled '+' icon that appears alongside this parameter in the test configuration page. To know how to use this special page, refer to Configuring the Omnissa Horizon Connection Servers for Monitoring. |
User Name, Password and Confirm Password |
By default, this test uses Omnissa Restful APIs to collect the required metrics from the target Omnissa Horizon Cluster/Pod. For this, the eG agent should be configured with read-only user privileges that will allow the agent to communicate with the Horizon Connection Server in a particular domain and extract statistics. Therefore, specify the credentials of the user who is authorized to access the Horizon Connection Server against the User Name, Password and Confirm Password text boxes. |
Domain Name |
Specify the name of the domain to which the Horizon Connection Server belongs to. |
Measurement | Description | Measurement Unit | Interpretation | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Endpoint status |
Indicates the current status of the endpoint on this connection server. |
|
The values that this measure can take and its corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the above-mentioned Measure Values to indicate the current status of the endpoint on each connection server. However, the graph of this measure will represent the same using the numeric equivalents only i.e., 1 to 3. |
||||||||
Round trip time |
Indicates the response time of this connection server. |
Milliseconds |
Compare the value of this measure to identify the remote Omnissa Horizon Connection Server that is slow to respond to requests. |
||||||||
Is endpoint enabled? |
Indicates whether/not the endpoint on this connection server is enabled. |
|
The values that this measure can take and its corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the above-mentioned Measure Values to indicate whether/not the endpoint on each Omnissa Horizon Connection Server is enabled. However, the graph of this measure will represent the same using the numeric equivalents only i.e., 0 or 1. |