Host Processes Test

This test monitors the specific processes executing on a server and reports the resource usage of the processes. This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Oracle Database as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the test : A server that supports the Host Resources MIB

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every configured process pattern

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed
  2. HOST - The host for which the test is to be configured
  3. snmpport - The port used to poll for SNMP statistics (default 161)
  4. SNMPVERSION – By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the snmpversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.
  5. SNMPCommunity – The SNMP community name that the test uses to communicate with the target host. This parameter is specific to SNMP v1 and v2 only. Therefore, if the snmpversion chosen is v3, then this parameter will not appear.
  6. username – This parameter appears only when v3 is selected as the snmpversion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against the username parameter.
  7. CONTEXT – This parameter appears only when v3 is selected as the SNMPVERSION. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the USERNAME provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the USERNAME in the CONTEXT text box.  By default, this parameter is set to none
  8. authpass – Specify the password that corresponds to the above-mentioned username. This parameter once again appears only if the snmpversion selected is v3.
  9. confirm password – Confirm the authpass by retyping it here.
  10. authtype – This parameter too appears only if v3 is selected as the snmpversion. From the authtype list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

    • md5 – Message Digest Algorithm
    • sha – Secure Hash Algorithm
  11. encryptflag – This flag appears only when v3 is selected as the snmpversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the encryptflag is set to no by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the yes option. 
  12. encrypttype – If the encryptflag is set to yes, then you will have to mention the encryption type by selecting an option from the encrypttype list. SNMP v3 supports the following encryption types:

    • des – Data Encryption Standard
    • AES – Advanced Encryption Standard
  13. encryptpassword – Specify the encryption password here.
  14. confirm password – Confirm the encryption password by retyping it here.
  15. TIMEOUT – Specify the duration (in seconds) beyond which the SNMP query executed by this test should time out. The default is 10 seconds.
  16. DATA OVER TCP - By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic - for instance, certain types of data traffic or traffic pertaining to specific components - to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the server over TCP (and not UDP). For this, set the DATA OVER TCP flag to Yes. By default, this flag is set to No.

  17. process - Should contain the specific processes to be monitored. Each process to be monitored is specified in the format “name:pattern”. The regular expression pattern denotes patterns that will be used to match processes on the server. For instance, to monitor all the Java processes on a server, specify the argument “java_processes:*java*”.
  18. useprocesspath - In some operating systems (example, OpenVMS), the process name in the HOST RESOURCES MIB will be an empty string, and the process path will include the process name. In such cases therefore, the test should be explicitly instructed to search the process path strings for the configured process names/patterns. To ensure this, set the useprocesspath parameter to true. By default, this parameter is set to false. Operating systems where process name (in the HOST RESOURCES MIB) is not an empty string can go with this default setting. 
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Processes running:

The number of processes currently executing on the server that match the pattern specified as parameter.


This value indicates if too many or too few processes corresponding to an application are executing on the host.

Memory utilization:

The total memory usage of all processes executing on the server that match the pattern specified as parameter. The memory usage is specified as a percentage of the total memory available on the server.


A very high value could indicate that processes corresponding to the specified pattern are consuming excessive memory resources.

Memory size:

The total memory usage(in MB) of all processes executing on the server that match the pattern specified as parameter.


A sudden increase in memory utilization for a process(es) may be indicative of memory leaks in the application.

CPU utilization:

The total CPU utilization of all processes executing on the server that match the configured process pattern.


A high value could signify a CPU bottleneck. The CPU utilization may be high because a few processes are consuming a lot of CPU, or because there are too many processes contending for a limited resource. Check the currently running processes to see the exact cause of the problem.