Horizon Cluster/Pod Overview Test

Using this test, the overall performance of the target Omnissa Horizon Cluster/Pod environment can be measured. This test helps administrators:

Track the count of connection servers, global entitlements, vcenters etc,
Identify problematic desktops and problematic RDS hosts
Figure out which protocol session is consistently used to access the target Cluster/Pod environment - is it Blast? or PCoIP? or RDP?
Analyze the gateway sessions and
Track replication information.

This way, this test can help understand the overall health, load and scaling of the target Omnissa Horizon Cluster/Pod environment.

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 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.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total connection servers	Indicates the total number of Omnissa Horizon Connection servers configured on the target Cluster/Pod.	Number	The detaiiled diagnosis of this measure lists the name of the Omnissa Horizon Connection servers configured on the target Cluster/Pod
Total vCenters	Indicates the total number of vCenters configured on the target Cluster/Pod.	Number
Total gateways	Indciates the total number of gateways (Unified Access Gateways) configured on the target Cluster/Pod.	Number
Global entitlements	Indicates the total Number of global entitlements configured on the target Cluster/Pod.	Number
Total desktop pools	Indicates the total number of desktop pools configured on the target Cluster/Pod.	Number
Total registered desktops	Indicates the total number of desktops that were registered.	Number
Total problematic desktops	Indicates the total number of desktops that were problematic.	Number
Total application pools	Indicates the total number of application pools configured on the target Cluster/Pod.	Number
Total farms	Indicates the total number of farms configured on the target Cluster/Pod.	Number
Total registered RDS hosts	Indicates the total number of RDS hosts that were registered.	Number
Total problematic RDS hosts	Indicates the total number of RDS hosts that were problematic.	Number
Total unique entitled users	Indicates the total number of unique users who are entitled to access the target Cluster/Pod.	Number
Total sessions	Indicates the total number of sessions initiated on the target Cluster/Pod.	Number
Total connected sessions	Indicates the total number of connected sessions during the last measurement period.	Number
Total disconnected sessions	Indicates the total number of disconnected sessions during the last measurement period.	Number
Total idle sessions	Indicates the total number of sessions that were idle during the last measurement period.	Number	A consistently high value of this measure indicates inefficient resource allocation and potential opportunities for optimization, such as automatically disconnecting idle sessions to free up resources for active users.
Total unique user sessions	Indicates the total number of sessions initiated by unique users during the last measurement period.	Number
Total unauthenticated sessions	Indicates the total number of unauthenticated sessions initiated during the last measurement period.	Number
HTML client type sessions	Indicates the total number of sessions initiated through HTML client type during the last measurement period.	Number
Windows client type sessions	Indicates the total number of sessions initiated through Windows client type during the last measurement period.	Number
Other client type sessions	Indicates the total number of sessions initiated through Other client types during the last measurement period.	Number
Sessions via Blast	Indicates the total number of sessions initiated through Blast protocol during the last measurement period.	Number
Sessions via PCoIP	Indicates the total number of sessions initiated through PCoIP protocol during the last measurement period.	Number
Sessions via RDP	Indicates the total number of sessions initiated through RDP during the last measurement period.	Number
Total internal gateway sessions	Indicates the total number of internal gateway sessions initiated during the last measurement period.	Number
Total external gateway sessions	Indicates the total number of external gateway sessions initiated during the last measurement period.	Number
Total unknown gateway sessions	Indicates the total number of unknown gateway sessions initiated during the last measurement period.	Number
Replication success status	Indicates the success of replication processes within the target Cluster/Pod environment.	Number	Replication success reflects whether data and configurations are being replicated correctly and efficiently between different components or sites. A successful status suggests healthy and consistent replication.
Replication error status	Indicates the replication errors occurring within the target Cluster/Pod environment.	Number	This measure reflects the health of the replication process responsible for maintaining data consistency across different sites or pods within the Horizon infrastructure. Whenever replication fails, it could potentially lead to data inconsistencies and impact the overall availability and performance of the target Horizon Cluster/Pod environment. Investigating the specific nature of the replication error is crucial for promptly resolving the issue and ensuring data integrity.