In the PROCESS text box, enter a comma separated list of names:pattern pairs which identify the process(es) associated with the server being considered. processName is a string that will be used for display purposes only. processPattern is an expression of the form - *expr* or expr or *expr or expr* or *expr1*expr2*... or expr1*expr2, etc. A leading ‘*’ signifies any number of leading characters, while a trailing ‘*’ signifies any number of trailing characters. The pattern(s) used vary from one application to another and must be configured per application. For example, for an iPlanet application server (Nas_server), there are three processes named kcs, kjs, and kxs associated with the application server. For this server type, in the PROCESS text box, enter kcsProcess:*kcs*, kjsProcess:*kjs*, kxsProcess:*kxs*, where * denotes zero or more characters. Other special characters such as slashes (\) can also be used while defining the process pattern. For example, if a server's root directory is /home/egurkha/apache and the server executable named httpd exists in the bin directory, then, the process pattern is “*/home/egurkha/apache/bin/httpd*”.

Note:

The PROCESS parameter supports process patterns containing the ~ character.

To determine the process pattern to use for your application, on Windows environments, look for the process name(s) in the Task Manager -> Processes selection. To determine the process pattern to use on Unix environments, use the ps command (e.g., the command "ps -e -o pid,args" can be used to determine the processes running on the target system; from this, choose the processes of interest to you).

Also, while monitoring processes on Windows, if the WIDE parameter of this test is set to true, then your process patterns can include the full path to the process and/or the arguments supported by the process. For instance, your PROCESSPATTERN specification can be as follows:

Terminal:C:\WINDOWS\System32\svchost -k
DcomLaunch,Remote:C:\WINDOWS\system32\svchost.exe -k netsvcs

Also, note that the PROCESS parameter is case-sensitive in Unix environments.

To save the time and effort involved in manual process specification, eG Enterprise offers an easy-to-use auto-configure option in the form of a View/Configure button that is available next to the PROCESS text box.

The procedure for auto-configuring the process(es) is as follows:

1. When the View/Configure () icon next to the PROCESS text area is clicked, a PROCESS CONFIGURATION page will appear.
Note:

The View/Configure () icon will appear only if the following conditions are fulfilled:

• The test must be executed in an agent-based manner.
• The eG agent executing the test should be of version 5.2 or above.
• In case the eG manager in question is part of a redundant manager setup, then the agent executing the test must be reporting metrics to the primary manager only.
2. Upon clicking the Get Processes button in the PROCESS CONFIGURATION page, a pop up window with a list of processes that are running on the host will be displayed.

Note:

The processes that are configured already will not be listed in the list of unconfigured processes.
3. The Click here link in the pop up window is used to view the processes either in a concise or in a detailed manner i.e. along with the process path and arguments.
4. Regardless of the view you are in, select the process or list of processes that require monitoring and click the SUBMIT button. Note that you can select processes from both the views.

Note:

The Processes test includes a WIDE flag that is set to Yes by default. In this case, your PROCESS specification can include the process path and arguments (if any). Therefore, if the WIDE flag is set to Yes, then, the eG agent will report metrics for the process(es) that are selected in both the concise manner and detailed manner. If the WIDE flag is set to No, the eG agent will collect metrics only for the process(es) that are selected in a concise manner.

5. Clicking the SUBMIT button in the pop-up will automatically populate the Name and Pattern text boxes available in the PROCESS CONFIGURATION page, with the name and pattern of the chosen process.
6. You can add more name:pattern pairs in the PROCESS CONFIGURATION page by clicking on the encircled ‘+’ button present at the end of the first Name and Pattern specification. To remove a specification that pre-exists, just click on the encircled ‘-’ button that corresponds to it. The contents of the Name and Pattern text boxes can also be edited manually.

Note:

Duplicate processes will appear in the list of processes pop-up, provided the process description is different - for instance, if a ‘cmd.exe’ process and a ‘cmd.bat’ process execute on the same host, then both processes will be listed as ‘cmd’ in the ‘concise’ view of the process list. If such duplicate processes are chosen for monitoring, then, each process will appear as a separate Name and Pattern pair in the PROCESS CONFIGURATION page. To proceed, the user must enter a different name in the Name text box for each process, so that every distinct pattern can be identified in a unique manner.