ASAP 2.8 Server Manual

HP NonStop ASAP Server Manual—522303-007
5-1
5 File and Process Monitoring
ASAP provides various ways to monitor files and processes and to control the amount
of data produced for those objects. The most common method of monitoring a file or
process is to specify the Guardian file or process name using the ASAP MONITOR
command. For example, the commands MONITOR FILE $DATA.SUBVOL.FILE and
MONITOR PROCESS $ABC will configure ASAP to monitor file $DATA.SUBVOL.FILE
and process $ABC. This section discusses more uncommon ways to monitor files and
processes using ASAP, which include:
•
Monitoring files and processes using wild-card names
•
Monitoring all the processes running from an object file
•
Monitoring OSS files
•
Monitoring processes executing from an OSS object file
•
Grouping files into logical, hierarchical groups of files
•
Grouping processes into logical, hierarchical groups of processes
•
Defining aggregate and aggregate-only domains at any level of the name hierarchy
Specifying Wildcard Names
You can use the "*" and "?" wildcard characters to specify Guardian file or process
names to monitor. Wildcards are not accepted at the volume name level of a filename.
Wildcards are only permissible in the subvolume and filename portions.
When wildcard names are specified, ASAP resolves the name at each interval to
determine if the files or processes meet the criteria, and ASAP computes and creates a
record for each object found. To avoid name conflicts with other forms of name
specifiers, ASAP appends the object name to the end of the name specified as a new
level of the ASAP domain name. For example, the command MONITOR PROCESS
$A* would resolve into a domain named "$A*\$ABC" for process $ABC.
Because the set of objects resolved from a wild-card name can vary at each interval,
ASAP will not issue an alert if it finds a member of the set is no longer running or
present. This is contrary to the way ASAP works if you directly monitor a file or process
without using wildcard names. In that case, ASAP does issue an alert when it cannot
find the file or process. ASAP does provide counts of objects when viewing the
wildcard domains at aggregate levels.
Wild-card names can resolve into many thousands of objects. That number of records
can put pressure on disk resources when storing historical data, so ASAP
automatically adds an aggregate-only domain to limit the output from wild-card name
specifiers after you issue a MONITOR command that contains a wild-card name. You
must manually delete the aggregate-only domain for individual records on each object
to be written to the historical database. For example if you enter MONITOR PROCESS
$A*, then ASAP issues a MONITOR PROCESS $A*\## command to add an