eG - Monitoring
 

Measures reported by VmgApplaunchTest

When a user complains that it is taking too long to launch applications on virtual/physical desktops, administrators must be able to quickly identify the applications that are being currently accessed by that user, know how much time each application took to launch, and thus pinpoint that application that is the slowest in launching. The VmgApplaunchTest test provides these valuable insights to the administrators.

This test auto-discovers all the applications that are currently launched on the virtual/physical desktops, and for each discovered application, reports the average and maximum time that application took to launch. This way, the test points administrators to applications that are slow in launching. Detailed diagnostics provided by the test also reveals the users who are currently accessing the applications and the launch time of the application as perceived by each user session; in the process, the test accurately pinpoints which user was attempting to launch the application when the slowness was observed.

Outputs of the test :One set of results for every application on a Physical/virtual desktop group that is currently launched.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
No_of_processes Represents the number of instances of this application that have been launched currently. Number Use the detailed diagnosis of this measure to know which users are currently accessing the application and the time it took for every user to launch the application.
Launch_duration Indicates the average time taken by this application to launch. Secs Compare the value of this measure across applications to know which application took the longest time to launch. User experience with this application will naturally be poor.
Max_launch_duration Indicates the maximum time taken by this application to launch. Secs Compare the value of this measure across applications to know which application registered the highest launch time during the last measurement period. To know which user experienced this delay in launching, use the detailed diagnosis of the No_of_processes measure.