ASAP 2.8 Server Manual

Introduction to Availability Statistics and

Performance (ASAP)

HP NonStop ASAP Server Manual—522303-007

1-5

Data Collection and Monitoring

ASAP monitors and reports high-level, real-time network availability and user-defined

application availability from one or more nodes. Availability information is sent to one or

more collection nodes within the network. You use ASAP to view and analyze real-time

or historical network-wide views of Application, Comm, CPU, Disk, Expand, File,

Hybrid, Node, Process, ProcessBusy, Query, RDF, Spooler, System, Tape, TCP/IP,

Telserv, and TMF availability. You can customize each node for monitoring all or a

subset of entity availability.

ASAP availability information is stored in the ASAP database for historic reference, as

well as for shared access by multiple users and applications. The ASAP Server

collects data with a set of CPU Monitors, Statistic Gathering processes (SGPs), and

Collection processes in a network of systems. ASAP monitors operational information

of system and user-defined resources. The ASAP SGPs report on performance and

operational information of system and user application resources. This information is

collected at defined intervals and forwarded to a Collection process residing on the

same or another node in the network. The Collection process maintains this

information in the ASAP database.

You can configure ASAP to gather performance and state information from multiple

nodes throughout the network. You can independently configure these nodes so some

nodes monitor Disk availability while other nodes do not. You can centralize data

collection to a single node, to groups of regional nodes, or completely distribute it so

each node in a network has its own ASAP availability database.

ASAP lets you monitor individual objects, by defining such objects with the MONITOR

command.

For example, in a 10 processor node, all ASAP SGPs let you get availability

information from all 10 CPUs or just from a few of them. You can separately set

individual thresholds for each object, such as CPU 0 can report EMS events to alert an

operator when the CPU is 45% busy, and send an alert if CPU 0 is less than 25% busy.

Meanwhile, you can set other individual thresholds for CPU 1 and all remaining CPUs

on the node.

ASAP also maintains time synchronization of nodes. You can configure it to

synchronize time daily at a specific interval. Remote node times are synchronized with

the Collection node.

The Collection process automatically creates and maintains the ASAP database files.

You can configure database maintenance options to automatically release files, purge

data, maintain a moving window of data over time, or turn off collection for a selected

period of time.

The ASAP database is a real-time structured database, organized so that the most

current network availability information is immediately available. If you need direct

programmatic access to the ASAP database, see the record description of each ASAP

entity in Appendix B, ASAP Data Definitions.