Application Access - AVD Test

Applications hosted on the system communicate within the system environment and may also interact with external entities such as public APIs, internet resources, or remote users. One of the key factors influencing the responsiveness of these applications is the latency experienced while handling internal and external communications. Prolonged response times often lead to delays, degraded user experience, system instability, and potential application timeouts. To ensure a seamless user experience, administrators need to quickly identify which applications are slow to respond, determine the source of the delay, and understand whether the latency is due to internal system communication or interaction with external resources.

This test helps achieve this by auto-discovering the applications running on the system and reporting metrics such as average and maximum latency, TCP connection counts, data sent/received, and total application traffic. For each application, the test also reveals the PID, connection type, and the direction of communication. This helps pinpoint applications with performance issues and assists in troubleshooting slow or unresponsive applications on the system.

Target of the test : An Azure Virtual Desktop

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each connection type:application on the target system.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The default port is NULL.
Monitor Latency For	Select the application processes to be monitored from the Monitor Latency For drop-down list. By default, All Processes will be selected, which means the test will report measurements for all application processes running on the system. If you want to monitor only whitelisted processes, choose the Whitelisted Processes option, this will configure the eG agent to monitor only those processes that have been predefined as whitelisted. 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. 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. To monitor specific processes, select the Selected Processes option from the drop-down, and then provide the list of process names in the Application Processes for Latency Monitoring parameter.
Application Processes For Latency Monitoring	By default, the value of this measure is set to none. However, if you configure the Monitor Latency For parameter to Selected Processes, you must provide a comma-separated list of the application processes you wish to monitor. The list can be specified in any of the following formats: processName1, processName2 processName1@remoteIPAddress,processName2@remoteIPAddress processName1@remoteIPAddress;port,processName2@remoteIPAddress;port
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 server, by default. If you want the test to disregard certain applications when monitoring, then provide a comma-separated list of process names that correspond to the applications you want to ignore, in the Exclude text box. 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. For instance, if you set to 6:1, it means that detailed measures will be generated every time this test runs, and also every time the test detects a problem.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG suite 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
Total application traffic	Indicates the total volume of network traffic handled by this application process, calculated as the sum of data transmitted and data received.	KB/sec	A high value may indicate that the application process is actively handling a large number of requests or data-heavy operations. A sudden spike might suggest abnormal activity or heavy usage.