AppStream Application Access Test

Applications hosted on the AWS AppStream Multi-Session Host communicate within the AppStream environment or private network and also interact with entities outside the private network, such as public APIs, internet resources, or external end-users. One of the key factors influencing the efficiency of internal/external communications of the applications is the latency experienced by the applications when responding to other applications within the AppStream environment, as well as to external entities. Frequent / prolonged time lags experienced by the applications often results in delayed responses and communication failures within the AppStream environment and as well as during external application streaming. This in turn can increase user frustration, impact productivity, affect revenues, and escalate costs. This is why, when a user complains about delayed/poor responses or failures while accessing the applications, administrators must be able to quickly identify these applications, determine how much time each application took to respond to requests from internal/external connections, and thus pinpoint the application that is the slowest in responding. The AppStream Application Access test assists with this.

This test auto-discovers the applications, and for each application, reports the average and maximum latency experienced while responding to the internal and external requests. This way, the test points to the highly latent applications that could be degrading user experience and also enable users to quickly identify whether the high latency is experienced during interaction within or outside the AppStream environment. In addition, this test also reports the count of TCP connections established by each application. The detailed diagnosis reported by this test reveals the PID associated with each application process, the rate at which the data was sent/received by a process, the total amount of data transmitted and received per second, the latency experienced by each process in seconds and connection type of each application process.

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 connection type:application on the target host

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.
Monitor Latency For and Application Processes for Latency Monitoring	By default, "All processes" option is selected from the Monitor Latency For list indicating that this test will monitor latency experienced by all processes launched during the execution of applications. However, if you prefer this test to monitor certain critical processes launched during the execution of the applications, select the Selected processes option from this list and specify a comma-separated list of process names against the Application Processes for Latency Monitoring 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. By default, this parameter is set to none.
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, if 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: notepad.exe,paint.exe,excel.exe. Your specification can include wild card patterns as well. For example: *note*,paint*,*excel
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
Process instances	Indicates the number of process instances of this application currently running on the target host.	Number
TCP connections	Indicates the number of TCP connections established by the processes of this application.	Number	The detailed diagnosis of this measure reveals PID of each application process that established the TCP connection, local and remote IP addresses and ports used by each TCP connection, the rate at which the data was transmitted and received through each connection, the total amount of data transmitted and received through each connection per second, and the latency experienced by each connection in seconds.
Avg latency	Indicates the average latency experienced by the processes of this application while responding to user requests. The value reported is the average of latencies experienced by all processes of an application.	Seconds	A consistently high latency may be indicative of poor responsiveness of applications which adversely impacts user experience with the target multi-session host. Possible reasons for an increase in latency could be increased network delays, network congestion, server slow-down, too many simultaneous users on the server etc. Comparing the value of this measure across applications will enable administrators to quickly and accurately identify applications that are experiencing higher latency when delivering services to users.
Max latency	Indicates the maximum latency experienced by the processes of this application while responding to user requests. The value reported is the maximum latency experienced by one of the processes of this application.	Seconds
Data transmitted	Indicates the rate at which the data was transmitted by the processes of this application.	KB/sec
Data received	Indicates the rate at which the data was received by the processes of this application.	KB/sec