ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 135 of 381
Creating Specific Aggregate-Only Domains (Recommended)
To cause ASAP to write only the aggregate record for a set of domains, use the
MONITOR command to add an aggregate domain using ## as the last level specifier.
For example, the command MONITOR PROCESS SALES\## causes ASAP to write
only the Sales\## record to disk. ASAP still computes data for each individual process
and then combines the data into the aggregate record, but it writes only the aggregate
record to disk.
Setting Global Aggregate Only for All Domains
An ASAPCONF parameter setting for File and Process, AGGONLY, causes ASAP to
automatically create aggregate records at each level of any hierarchical process name
and to write only the aggregate domains to the database. If AGGONLY is defined, you
need not add aggregate domains to the database. ASAP automatically creates them.
Aggregation Defined
The way attribute values are combined in the aggregate records varies by attribute and
can be changed. Different users might want different behavior for a specific attribute.
For example, consider the Process Busy, Pri and PFName attributes. (Busy represents
process busy.) By default, ASAP sums all the process busy values in the group for the
aggregate record, so you can see the total consumption of processor resources across
the group.
However, it does not make sense to sum the values of the Pri attribute, which
represents the priority of the processes. ASAP assumes you are interested in the
process with the lowest priority, by default, so it uses the minimum Pri attribute value
found among all processes in the group when creating the Pri value in the summary
record.
Also consider the PFName attribute that contains the object file name for each
process. It does not make sense to perform any calculations on that attribute in the
summary record. For PFName and several other process attributes, ASAP propagates
the value to the summary record from the process with the highest (worst) ASAP state.
For example, if there are 100 processes, with two issuing a critical alert (ASAP state 7)
and one issuing a down alert (state 8), ASAP propagates the PFName value from the
down process to the summary record. If multiple processes have the same worst state,
the first one found is propagated to the summary record.
ASAP gives you control over how data is ultimately combined in the aggregate record.
See the next subsections.
State Propagation
ASAP always propagates the worst state for each attribute to the aggregate record
regardless of how the attribute value is computed in the aggregate record unless