ASAP 2.8 Server Manual

File and Process Monitoring
HP NonStop ASAP Server Manual—522303-007
5-6
Aggregation Defined
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
specific objectives are set on the attribute at the aggregate level. The state associated
with the value in an aggregate record might or might not reflect the actual state of the
value shown. Consider the Process Busy attribute. In the aggregate record, ASAP
combines all the process busy attribute values in the group to show the total processor
consumption of the group. However, the state shown for that attribute, unless
overridden by setting a specific objective at the aggregate level, represents the worst
state found for the busy attribute among all the members.
For example, consider a group of five processes, Sales\$A10 through Sales\$A15.
ASAP combines all five process busy attributes when it creates the Sales\# domain,
showing the total consumption of all five processes. However, if process $A13 is
issuing an alert because it is too busy, that alert level is propagated to the aggregate
domain. Setting specific objectives on an aggregate domain overrides state
propagation. For example, RANK SALES\#, BUSY < 20 sets an objective on the
Busy attribute at the aggregate level, and the result of that objective comparison
produces the ASAP state for Busy, not the propagated state value.