AppStream Application Process Launches Test

When a user complains that it is taking too long to launch applications on the AWS AppStream Multi-session Host that is being monitored, 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 AppStream Application Process Launches test provides these valuable insights to the administrators. This test auto-discovers all the applications that are currently launched on the target host, 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.

Target of the test : An AWS AppStream Multi-session Host

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each application that is being monitored

Configurable parameters for the test
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 at which the target host listens.

Report By Domain name

  • By default, this flag is set to Yes. This implies that by default, the detailed diagnosis of this test will display the domainname\username of each user who accessed an application on the host. This way, administrators will be able to quickly determine which user logged into the host from which domain. If you want the detailed diagnosis to display only the username of these users, set this flag to No.
  • Show Only Whitelist Apps

    In some highly secure virtual environments, administrators whitelist an index of business-critical and most commonly used applications that are permitted to be present and active on the target host. The goal of whitelisting is to protect the target server from potentially harmful applications and prevent any unauthorized files from executing. Application whitelisting places control over which applications are permitted to run on the target server and is controlled by the administrators, rather than the end-user. In such environments, administrators may wish to monitor only the applications that are whitelisted on the target host. To achieve this, administrators can set the Show Only Whitelist Apps flag to Yes.

    By default, this flag is set to No indicating that this test monitors all applications executing on the target server. By default, eG Enterprise offers a comma separated list of pre-defined applications specified against the WhiteListProcesses option in the [EXCLUDE_APPLICATIONS] section of the eg_tests.ini file available in the <eG_INSTALL_DIR>/manager/config folder. Setting the Show Only Whitelist Apps flag to Yes will enable this test to monitor only the applications that are listed against the WhiteListProcesses option. If administrators wish to add or remove one or more applications to/from this pre-defined list, then, they can do so by specifying the applications against the WhiteListProcesses option.

    Exclude

    By default, this parameter is set to none. This means that the test will monitor all the applications that are launched on the target host, by default. However, ff you want this test to disregard certain applications when monitoring, then provide a comma-separated list of process names that correspond to the applications that you want to ignore, against this parameter. For instance, your specification can be: winword.exe,js.exe,taskmgr.exe. Your specification can include wild card patterns as well. For example: *win*,js*,*task

    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:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
    Measurements made by the test
    Measurement Description Measurement Unit Interpretation

    Launch count

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

    Avg time to launch application

    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 time to launch application

    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 Launch count measure.