Availability Guide for Problem Management

Monitoring Objects
Availability Guide for Problem Management–125509
5-4
Commonly Monitored Objects
Object Behavior
For each object identified, you should define its valid states, state transitions, possible
conditions that make it change states (such as a user command or an internal error in the
subsystem), and the corresponding actions. For each state change caused by an internal
or external condition, the object may have a predefined set of actions. Often, the action
is to generate an EMS event message that informs the system of the object’s state
change.
Commonly Monitored Objects
Objects that are commonly monitored and that provide helpful information about the
health of your system environment include the following:
•
Processors
•
Disks
•
Files
•
Processes
•
Spooler components
•
Audit trails
•
NonStop Transaction Manager/MP (TM/MP) transactions
•
Tape mount requests
The Three Types of Object Monitoring
Tandem systems provide three different types of object monitoring to help you predict,
prevent, and detect unplanned outages in your environment, as follows:
•
Object state monitoring
•
Performance monitoring
•
Critical resource monitoring