Horizon Cloud Logon Details Test
Logon metrics were previously obtained from within a VDI or a multi-session host. Starting with Horizon v8, some of the details being collected by eG agents/VM agents from the RDSH server and VDIs are not available any longer. Logon monitoring is now supported using Horizon APIs by connecting to the Horizon control plane (on-prem or cloud). Logon performance breakdown is now provided as part of the Horizon Cluster Pod model (similar to how logon metrics are provided for Citrix and AVD technologies). This methodology ensures that logon time breakdowns are also now available for Linux VDIs
The Horizon Cloud Logon Details test monitors user logins to the desktops/applications in the target Omnissa Horizon Cloud Control Plane, measures the ‘aggregate’ duration of the login across all users, and thus points to bottlenecks in the user logon process.
This test on the other hand, provides the user-perspective to logon monitoring. In other words, this test tracks each user who logs into a desktop or accesses an application, reports in real-time the logon experience of that user, and pinpoints where exactly that user’s logon slowed down. When a user complaints of delays in accessing his/her virtual desktop, this test will lead administrators straight to what is causing the delay. Irrespective of desktop OS and deployment model, this test reports detailed logon performance breakdowns for all user logons.
Target of the test : Omnissa Horizon Cloud Control Plane
Agent deploying this test : A remote agent
Outputs of the test :One set of results for each user accessing desktops/applications in the target Omnissa Horizon Cloud Control Plane being monitored.
| Parameters | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port to which the specified host listens. |
|
API Client ID |
The API Client ID uniquely identifies the client application or user making requests to the control plane. It serves as a way to verify who is making the API call, ensuring that the request is coming from an authorized source. Specify the API Client ID in the API Client ID text box. To create the API Client ID, refer to How Does eG Enterprise Monitor Omnissa Horizon Cloud Control Plane?. |
|
API Client Secret |
The API client secret works alongside the API client ID to authenticate the client making the API request. While the Client ID identifies the client, the Client Secret serves as a password to verify the identity of the client. This ensures that only authorized clients can interact with the control plane. Specify the API Client Secret in the API Client Secret text box. To create the API Client Secret, refer to How Does eG Enterprise Monitor Omnissa Horizon Cloud Control Plane?. |
|
Confirm Password |
Confirm the API Client Secret by retyping the same in the Confirm Password text box. |
|
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. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
Has user session been reconnected? |
Indicates the connectivity status of session for this user. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the connectivity status of session for this user. The graph of this measure however, is represented using the numeric equivalents only. The detailed diagnosis for this measure provides the details such as User Name, Session Status, Session Type, Session ID, Login Time, Pool Name, Pool Type, Desktop Name, Client IP, Client Type, Client Protocol, Edge Name, Logon Duration, Shell Load Time, Profile Load Time, and Remaining Duration. |
||||||
|
Number of sessions |
Indicates the total number of sessions for this user. |
Number |
The detailed diagnosis for this measure provides the details such as Is session reconnected, User Name, Session Status, Session Type, Session ID, Login Time, Pool Name, Pool Type, Desktop Name, Client IP, Client Type, Client Protocol, Edge Name, Logon Duration(seconds), Shell Load Time(seconds), Profile Load Time(seconds), and Remaining Duration(seconds). |
||||||
|
Average logon duration |
Indicates the average time taken for this user to login to desktops/access applications. |
Seconds |
If this measure reports a high value consistently, it could indicate a slowdown in the logon process. Compare the value of this measure across users to know which user’s logon is taking the longest. |
||||||
|
Shell load duration |
Indicates the duration between the initialization of the user interface to the time the user receives keyboard and mouse control. |
Seconds |
|
||||||
|
Profile load duration |
Indicates the time taken by the logon process to load the profile of this user. |
Seconds |
|
||||||
|
Other processing duration |
Indicates the time taken by this user to perform processes other than logon related processes. |
Seconds |
|