Writer instructions
Page title	For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n.
Purpose	Provide an announcement banner on every page of your space.
Location	Move this page outside of your home branch.
Guidelines	Adding-a-banner-announcement-to-a-space

Monitoring Process Presence

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

Drill down into the PROCESS container instance.
Select the PROCESS_PRESENCE icon and right-click to open its menu.
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

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.

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.