Horizon Cluster/POD Broker Access Test

In an Omnissa Horizon Cloud environment, the availability of the Omnissa Horizon Cluster/Pod round the clock is imperative to ensure that users have uninterrupted access to the applications/desktops provisioned through Omnissa Horizon Connection servers. A Omnissa Horizon Cluster/Pod may sometimes be unavailable owing to many reasons – e.g., an internal configuration error, hardware failure, service outage, connectivity issues etc. Administrators should proactively be alerted to such unavailability of the Cluster/Pod so that they can initiate troubleshooting much before end users start complaining. The Horizon Cluster/POD Broker Access test helps administrators track the unavailability of the target Omnissa Horizon Cluster/Pod.

This test instantly informs administrators of the non-availability (if any) of the target Omnissa Horizon Cluster/Pod and also intimates them of any probable slowdown in the responsiveness of the Cluster/Pod.

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 the target Omnissa Horizon Cluster/Pod being monitored

Configurable parameters for the test
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.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Availability	Indicates the availability of the target Cluster/Pod.	Percent	Availability failures could be caused by several factors such as the server process(es) being down, the server being misconfigured, a network failure, etc. Temporary unavailability may also occur if the Cluster/Pod is overloaded. The value 100% for this measure indicates that the target Horizon Cluster/Pod is available, and the value 0 indicates that it is not.
Response time	Indicates the time taken by the target Horizon Cluster/Pod to respond to the HTTP / HTTPS requests received.	Seconds	If the value of this measure consistently increases, it indicates that the performance of the target Horizon Cluster/Pod is gradually deteriorating. Ideally, the value of this measure should be low.