ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 137 of 381
Attribute Propagation
If no aggregation rule is defined for an attribute, the value associated with the attribute
with the worst state is also propagated. For example, if you remove the SUM rule from
the Process Busy attribute in the previous example, the Busy value for process
Sales\$A13 is propagated to the aggregate record instead of the sum of all processes.
By default, all File attribute values are propagated to the aggregate record. By default,
Process attribute values vary based on the MetricRule property.
Status and OpState
The Status attribute is handled differently than other attributes in an aggregate record.
The Status text field is used to show the number of members of the group and the
number that are issuing alerts. For example, if there are five files in the group and
there are no alerts, the Status text reads "5 Files." If there are five processes in the
group with one issuing alerts, the text reads "5(1) Processes."
The state at which ASAP considers a file or process to be alerting is the Low Alert
state 3, so if any attribute in the domain record has a state of 3 or higher, the domain is
counted in the number of alerting domains shown in the Status text field. If you prefer a
different alert level, you can change the state at which ASAP considers a process to be
alerting. See the FILE and PROCESS options for the SET Command.
ASAP Alert Levels:
1
Exists
2
OK
3
Low Alert
4
Medium Alert
5
High Alert
6
Warning
7
Critical
8
Down
The associated state for Status, OpState, is propagated from the worst state within the
set like all other state attributes.