Auto-configuring the Process Patterns to be Monitored

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.

To auto-configure the processes to be monitored, do the following: Note:

The Processes test of LDAP servers takes an additional parameter named ISPASSIVE. If the value chosen against this parameter is Yes, then the LDAP server under consideration is a passive server in an LDAP cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

Note:

 Administrators can extend the built-in auto-correction capabilities to address probable issues with the other measures of the Processes test, by writing their own corrective scripts for the same. The custom-defined script can be associated with the Processes test in the same manner discussed above.

 The name of the custom-defined script should be of the following format:

InternalTestName_InternalMeasureName. For example, a script that is written to correct problems with the CPU utilization measure (of the Processes test) should be named as "ProcessTest_Cpu_util”, where ProcessTest is the internal name of the Processes test, and Cpu_util

is the internal name for the CPU utilization measure. To know the internal names of tests and measures, use any of the eg_lang*.ini file in the <EG_INSTALL_DIR>\manager\config directory. The script extensions will differ according to the operating system on which it will execute. The extensions supported by Windows environments are: .bat, .exe, .com, and .cmd. Scripts to be executed on Unix environments do not require any extension. The most commonly used extension is .sh.

 At any given point of time, only one script can be specified in the CORRECTIVESCRIPT text box.

 As already stated, the sample script for Processes test will be available for every operating system. If the script is uploaded to the eG manager once for an operating system, it will automatically apply to all the agents executing on the same operating system. For example, say that an environment comprises of 3 agents, all executing on Windows 2000 environments. While configuring the Processes test for one of the agents, if the administrator uploads the sample script, then he/she will not have to repeat the process for the other 2 agents.

 Once the eG agent downloads a corrective script from the eG manager, any changes made to the script in the manager side will not be reflected in the agent side, immediately. This is because, the eG agent checks the manager for the existence of an updated version of the corrective script, only once a day. If an update is available, the agent downloads the same and overwrites the script that pre-exists.

1. Click on the View/Configure button next to the PROCESS text area in the Processes test configuration page (see Figure 2.16).

Figure 2.16: Configuring the Processes test

2. When the View/Configure button is clicked, a PROCESS CONFIGURATION page will appear (see Figure 2.17).

Figure 2.17: Auto-configuring the processes to be monitored

3. 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 (see Figure 2.18).

Note:

The View/Configure button will appear only if the following conditions are fulfilled:

 The Processes 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.

Figure 2.18: List of auto-discovered processes

4. By default, Figure 2.18 provides a 'concise' view of the process list - i.e., only the process names will be listed in the pop-up window, and not the detailed description of the processes. You can click on the Click here link in the pop up window to switch to the detailed view (see Figure 2.19).

Figure 2.19: The detailed view of processes

5. As you can see, in the detailed view, the complete process path and process arguments accompany each auto- discovered process.

Note:

6. Regardless of the view you are in, select the process or list of processes that require monitoring and click the

SUBMIT button in the pop-up window. Note that you can select processes from both the views.

7. 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 (see Figure 2.20).

Figure 2.20: Multiple auto-discovered processes configured for monitoring

8. 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.