eG Monitoring
 

Measures reported by HrznAppLaunchTest

The virtual desktops/applications are launched by clients on the VMware Horizon View Connection server. To know the exact number of applications that were launched and the average time taken to launch an application, use the HrznAppLaunchTest test. Using this test, you can also figure out the number of applications that failed to launch and the maximum time taken to launch an application. This way, administrators can identify those applications that took too long to launch and the users who attempted to launch the applications.

Outputs of the test: One set of results for the VMware Horizon View Connection server being monitored

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Launched_app Indicates the number of applications that were launched. Number The detailed diagnosis of this measure if enabled, lists the applications that were launched, the session ID, the username, the time taken to launch the application, the machine ID, the server address and server port, the Client IP address etc.
Max_time Indicates the maximum time taken to launch an application. Secs The detailed diagnosis of this measure helps you to identify the application that took too long to be launched. The detailed diagnosis of this measure if enabled lists the Session ID, the user who is accessing the application, the time taken to launch the application (in secs), the machine ID, the server address, the server port, the server protocol and the client IP address.
Avg_time Indicates the average time taken to launch the applications. Secs A high value for this measure is a cause of concern.
Failed_app Indicates the number of applications that failed. Number The detailed diagnosis of this measure if enabled, lists the Session ID, the user who is accessing the desktop, the Client IP, the Client address, the error message describing the reason for the failure of the desktops.

Note:

If a value less than a minute is configured as the TEST PERIOD of this test, then, the Uptime measure will report the value 0 for Unix VMs (only) until the minute boundary is crossed. For instance, if you configure this test to run every 10 seconds, then, for the first 5 test execution cycles (i.e., 10 x 5 = 50 seconds), the Uptime measure will report the value 0 for Unix VMs; however, the sixth time the test executes (i.e, when test execution touches the 1 minute boundary), this measure will report the value 60 seconds for the same VMs. Thereafter, every sixth measurement period will report 60 seconds as the uptime of the Unix VMs. This is because, Unix-based operating systems report uptime only in minutes and not in seconds.