ASAP 3.0 QuickStart Guide

HP NonStop ASAP QuickStart Guide Page 27 of 35
Section 5: Setting Goals
When you first start ASAP Server and Client and configure the set of objects you are
interested in, ASAP will begin monitoring those objects and will display them in the ASAP
Client. Optionally, you can also view data using the ASAP CI commands on your NonStop
Server. We recommend that you run ASAP for a period of time before moving to this step,
so that you better understand the performance profile of your objects.
Once you know what the normal operational and performance characteristics of your
systems are, then read this section to learn how to configure ASAP to set goals around your
normal system characteristics so that you can be alerted when abnormal conditions occur.
Alerting on Status
ASAP automatically alerts when status changes occur for objects you are monitoring. For
example, if a monitored CPU fails, ASAP will automatically alert you to that condition by
highlighting the CPU in red on ASAP Client and showing its status as Down. ASAP will also
create an EMS event notifying you of the condition if configured to do so. ASAP will alert
you for many status change conditions, for example if a Disk drive fails, a Disk path
switches, a monitored Process fails, an Expand line goes down, etc.
ASAP uses the Status attribute for each entity (monitored subsystem) to both report the
status as well as issue alerts about the status of each domain (monitored object) within that
entity. The Status attribute is in the attribute-set for every entity. It is a special attribute
since it is set directly by ASAP based on its determination of the status of the specific object
it is monitoring. You are not allowed to set goals on a Status attribute, however you can
control whether or not EMS events are generated and if they are single events or if they
repeat at each interval.
Alerting on Other Attributes
ASAP Client will alert on other attributes when it is first installed because by default it uses
Client-specific threshold values to determine alert levels. Because these levels are Client-
specific, no EMS events are generated. To set host-based pre-defined goals for attributes,
you use the GOAL command and you also change ASAP Client to use your goals for
alerting (see the next Section on configuring ASAP Client to use host-based goals.)
By default, ASAP Server does not generate host-based alerts on any attribute other than the
Status attribute because it cannot know what attribute values cause problems in your
particular environment. For example, on some systems a CPU BUSY value of 90% would
indicate a problem, but on another system it would not.
To set pre-defined goals, use the GOAL command. For example, the following command
sets a goal on the CPU BUSY attribute: