eG EXEC Process Test

Administrators can optionally configure the eG manager to run each of its critical functions - i.e., email alert management, threshold computation, trending, and database cleanup activities - as separate processes, so that additional memory is available for the core eG manager functions such as data reception and analysis, alarm correlation, and web-based access and reporting. Using this test, you can identify the manager functions that have been set to execute as separate processes. The test also sheds light on situations where more than one instance of a process may be running, so that you can conserve resources by terminating the unnecessary instances.

Target of the test : The eG Manager

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for critical eG manager function.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed .


The host for which the test is to be configured.


The port number at which the specified host listens.

JMX Remote Port

Here, specify the port at which the JMX listens for requests from remote hosts. In the <EG_MANAGER_INSTALL_DIR>\manager directory (on Windows; on Unix, this will be the /opt/egurkha/manager directory) of the eG manager, you will find a file. Set the port defined against the parameter of the file as the JMX Remote Port.

User, Password, and Confirm Password

By default, JMX requires no authentication or security. Therefore, the User, Password , and Confirm Password parameters are set to none by default.


The JNDIName is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.

JMX Provider

This test uses a JMX Provider to access the MBean attributes of the eG manager and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.


Specify the duration (in seconds) for which this test should wait for a response from the eG manager. If there is no response from the eG manager beyond the configured duration, the test will timeout. By default, this is set to 240 seconds.

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 count

Indicates the number of instances of this process that is currently running.


The test will report this measure only if the value of the 'Is EXEC process?’ measure is ‘Yes’.

The value 1 is desired for this measure. Any value above 1 is a sign that more instances of a process are unnecessarily running and draining resources. Use the detailed diagnosis of this measure to know the process ID of the additional processes, so that you can kill them to conserve resources.

Is EXEC process?

Indicates whether this critical manager function has been configured to execute as a separate process.


The values that this measure can report and their corresponding numeric values have been listed in the table below:

Measure Value Numeric Value
Yes 1
No 0

It is recommended that the critical manager functions of email alert management, threshold computation, trending, and database cleanup activities are configured to run as separate processes. This is because, removing these key functions from the core eG manager process makes additional memory available for the core eG manager functions including data reception and analysis, alarm correlation, and web-based access and reporting. In addition, it also allows the eG manager to make better utilization of available server hardware resources and thereby offers enhanced scalability. In turn, this allows customers to get more leverage from their existing investment in the hardware that hosts the eG manager.


By default, the test reports the Measure Values listed in the table above to indicate whether a function has been set to run as a separate process or not. In the graph of this measure however, the same is represented using the numeric equivalents only.