Not Responding Processes – OS Test

A "not responding process" in a VDI (Virtual Desktop Infrastructure) environment typically refers to a software process or application running within the virtual desktop session that has become unresponsive or has frozen. This means the application or process is no longer performing its expected tasks, and its state has stalled, often requiring intervention to resume normal operation. This can be caused by various issues, including resource constraints (CPU, memory, network), application crashes, configuration problems, or underlying infrastructure issues. Diagnosing the issue involves checking system performance, network connectivity, and logs, and addressing the root cause - whether it’s resource overload, application conflicts, or infrastructure problems. Proactive monitoring, proper resource allocation, and regular system maintenance can help prevent such issues in VDI environments.

This test monitors the processes and reports the number of processes that are not responsive. Administrators may drill down to find the cause and make proactive measures to prevent such issues thereafter.

Target of the test : An Omnissa Horizon desktop on the cloud

Agent deploying the test : A Remote agent

Outputs of the test : One set of results for the target virtual server to be monitored.

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	Refers to the port at which the specified host listens to. By default, this is NULL.
Inside View Using	To obtain the 'inside view' of performance of the cloud-hosted virtual desktops - i.e., to measure the internal performance of the virtual desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent.
Report By User	This flag is set to Yes by default. The value of this flag cannot be changed. This implies that the virtual machines in VDI environments will always be identified using the login name of the user. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename.
Report Powered OS	This flag is relevant only for those tests that are mapped to the Inside View of Desktops layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those virtual desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_virtualdesktopname. On the other hand, if this flag is set to No, then this test will not report measures for those virtual desktops to which no users are logged in currently.
Is Cloud VMs	Since this test runs for every virtual desktops component which is a cloud-hosted desktop group, this flag is set to Yes by default.
Show Whitelist Process	In some highly secure environments, administrators whitelist an index of business-critical and most commonly used applications that are permitted to be present and active on the target physical machine. 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 server. 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.
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
Not responding processes	Indicates the number of processes that are not responding or frozen.	Number
Not responding processes end	Indicates the number of not responding processes that were terminated.	Number	This could happen when the RD (Remote Desktop) process is unresponsive and the session has timed out. If the process was repeatedly ending, further investigation into the process's dependencies or resource constraints might be needed.