ASAP 2.8 Server Manual

File and Process Monitoring
HP NonStop ASAP Server Manual—522303-007
5-8
Attributes without States
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 on page 6-87.
ASAP Alert Levels:
The associated state for Status, OpState, is propagated from the worst state within the
set like all other state attributes.
Attributes without States
Many attributes, such as the Process PFName attribute, have no associated state. You
cannot define an objective value on those attributes, and ASAP does not rank them.
For these attributes, ASAP propagates the values from the domain with the highest
alert level.
ASAP propagates these attributes regardless of any MetricRule setting for the
attribute:
File Attributes
Code Format Type Partitions LastOpen LastModif
Process Attributes
BPin Caid CLoc CreatedPaid PFName
PFS Pid Pin SMod SReq Type
Process PState and WState Attributes
The process state and wait state attributes cannot be combined using aggregate math
because each represents the unique state of an individual process. Typically, these
values are propagated to the aggregate record using the value from the attribute with
the worst state, but they can also be aggregated based on specific priority rules. This
1 Exists
2OK
3Low Alert
4 Medium Alert
5 High Alert
6 Warning
7Critical
8Down