Page tree
Skip to end of metadata
Go to start of metadata

Process Presence monitoring is available when using the Data Collection Manager (DCM) application and in the COLLECTORS mode.

Note

Host Group Process Presence monitoring does not work in PSL collection mode.

To define Process Presence entries for PATROL for UNIX and Linux

  1. Drill down into the PROCESS container instance.
  2. Select the PROCESS_PRESENCE icon and right-click to open its menu.
  3. Select Manage List of Monitored Processes from the menu.

    Note

    If the DCM collector is in use, the PROCESS instance might take some time to be created. The PROCESS_PRESENCE container instance too might take some time to be created.

Using Regular Expressions to Monitor Process Presence

You can use regular expressions defined by the REGEXP standard (REGEX API) to monitor process presence. However, because regular expression matching requires significant overhead, you should minimize its use. For example, if you want to match CRM80DM without getting CRM89DMO, use CRM89DM[^O] for the definition.

Agent Configuration Variables for Process Presence Monitoring

Following table contains descriptions of the variables used to monitor Process Presence.

Variables for Monitoring Process Presence

Variable

Description

/PUK/PROCCONT/daemonObjectList

Created automatically. If deleted, it will be automatically recreated Internal use only. PCM configuration is not recommended.

/PUK/PROCPRES/INSTANCE/info

Defines individual processes to be monitored. The following instances are created by default: ==> amd, defined by the REGEXP standard (REGEX, bind, cron, sendmail, and ypbind. Mirrors all hosts in the host group if the monitoring scope is across all hosts. When a new instance definition is discovered, a new PROCPRES instance is created and monitoring begins. Before using PCM to apply a configuration change to an existing definition, restart the Patrol Agent to reflect the change. One per instance. PCM configuration is allowed.

PUK/Process/Default/Created

Created automatically. Internal use only. PCM configuration is not recommended.

/UNIX/PROCCONT/processStamp

Automatically created when you add a new process using the Manage List of Monitored Processes menu. If deleted, it is not recreated until the next use of Manage List of Monitored Processes to add another new process. Internal use only. PCM configuration is not recommended.

/UNIX/PROCCONT/nodeList

Use of this option involves synchronization of several hosts and incorporates an encrypted password. Created when

  • You choose the Manage Host Group menu option. Defines list of hosts in host group.
  • A host group is established and mirrored on all hosts added to the host group. Must be consistent across all hosts in the Group Host List. If this variable is deleted from one or more of the hosts:
    • It is not automatically recreated.
    • The host will not respond to requests from any of the other hosts in the host group.
    • Attempts to use Synchronize=>Host Group will result in No Response.
    • When a new process is added to one of the other nodes in the Group Host List that has Monitoring Scope set to Across All Hosts, the process definition is mirrored on the host. However, the group host list is not automatically mirrored.
      PCM configuration is not recommended.

/UNIX/PROCCONT/nodeStamp

Created when the Manage Host Group menu option is used to define a host group. Internal use only. PCM configuration not recommended.

/UNIX/PROCCONT/eventTimeoutThe amount of time the knowledge module waits for acknowledgment from the other host, in the host group. While configuring the Host group, if the No Response message is displayed, add this variable in PATROL Agent configuration. The value of this variable is in seconds.

Using the /PUK/PROCPRES/INSTANCE/info Variable

Field definitions for the /PUK/PROCPRES/INSTANCE/info variable are closely aligned with the Add New Process dialog of Manage List of Monitored Processes menu option.

Process Instance Label

label

Monitored Process String

command string

Minimum Count

1

Maximum Count

1

Acceptable Process Owners

blank

Parent Process ID Must Be 1

NO (YES = 1, NO = 2)

Restart Automatically

NO (YES = 1, NO = 2)

Command Execution Attempts

5

Start Command

blank

Stop Command

blank

Command Execution User Name

blank

Command Execution Password

blank

Alert Delay Count

1

Alert State

ALARM (WARN = 1, ALARM = 2)

Monitoring Scope

Only on This Host (Only on This Host = 1, Across Host Group = 2)

Blackout Period start

0 (Hours) 0 (Minutes)

Blackout Period end

0 (Hours) 0 (Minutes)

Use Process Owners for Filtering

No (Yes = 1 and No = 2)

Note:  Because process filtering for processes is based on owners, the owner of the processes is always a subset of the provided owner set. Therefore, the PROCPPOwnerCheck parameter is deactivated when the Use Process Owners for Filtering check box is selected.

Filter Processes with Parent ID 1

No (Yes = 1 and No = 2)

Note:

  • If you select the Filter Processes with Parent Process ID 1 check box, only the processes having parent process ID 1 are filtered.
  • If you do not select the Filter Processes with Parent Process ID 1 check box, the processes are filtered irrespective of their parent process ID.
  • If you select Yes for the Parent Process ID Must Be 1 field, and if you filter processes with parent process ID 1, the PROCPPParentPID1 parameter will be deactivated.
  • If you select No for the Parent Process ID Must Be 1 field, the processes are not filtered by parent process ID 1.
 


You can apply the following example ruleset can by using Patrol Configuration Manager or pconfig to define two processes (newproc1 and newproc2).

{{PATROL_CONFIG "/PUK/PROCPRES/newproc1/info" = \{REPLACE = "newproc1^Bnewproc1^B1^B1^B^B2^B2^B5^B^B^B^B^B1^B2^B1^B0^B0^B0^B0^B0^B0"\}, "/PUK/PROCPRES/newproc2/info" = \{ REPLACE = "newproc2^Bnewproc2^B1^B1^B^B2^B2^B5^B^B^B^B^B1^B2^B1^B0^B0^B0^B0^B0^B0"\}}}

The field separator is CTRL-B. On a UNIX system, use the vi editor to enter the CTRL-B character.

Be careful when you manually edit configuration entries. You can start with a configuration that was generated by KMs with Process Presence for PATROL for UNIX. For example, use a ruleset captured from an existing configuration generated by using Process Presence to monitor KMs.

Using the /UNIX/PROCCONT/nodeList Variable

These are the field definitions for /UNIX/PROCCONT/nodeList variable. Do not use PCM or pconfig to apply this variable.

The node list consists of one or more nodes separated by the @ character. Each node specification consists of the hostname, port, username, and password fields separated by an * asterisk.

host1*portnumber*username*password@host2*portnumber*username*password@host3*portnumber*username*pasword@.

The host1 value must be the local host which runs the Patrol Agent.

  • No labels