OVNM 5.3 - Operations Agent for NonStop Event Management Guide for UNIX

HP NonStop Event Management System 12
2 HP NonStop Event Management System
2-1 Introduction to EMS
The Event Management Service (EMS) is a collection of processes, tools, and interfaces that support the reporting
and retrieval of event information.
Information retrieved from EMS helps you to:
• Monitor your system or network environment
• Analyze circumstances that led to a problem
• Detect failure patterns
• Adjust for changes in the run-time environment
• Recognize and handle critical problems
• Perform many other tasks required to maintain a productive computing operation
EMS is a major component of NonStop Kernel system management and was originally released on the D series
as part of the HP Distributed Systems Management (DSM) product group, which is described in the Introduction
to Distributed Systems Management (DSM).
EMS is used on both D-series and G-series releases of the NonStop Kernel.
2-1-1 EMS in the System Environment
EMS runs as a layer between the subsystem environment and the operations environment:
• In the subsystem environment, subsystem software directly controls resources (such as communication lines,
files, and processes). Subsystems can be HP products such as Pathway, components of DSM such as
ViewPoint, or user-written programs.
• In the operations environment, operations staff and specialized application programs (known as
management applications) obtain information needed to manage the system or network.
In the requester-server model, EMS acts as a server to both layers. It responds to requests from the subsystem
layer to accept and log event information, and responds to requests from the operations environment to retrieve
certain event information as needed.
Because events can occur at any time, a process that logs (or collects) events must run continuously. This process,
the primary collector ($0), is installed when the system is generated. EMS allows only one primary collector on
each node of a network.
In addition to the primary collector, you can define alternate collectors to provide separate logging facilities for
sorting selected events in separate log files. You can define as many alternate collectors on a system as you
want, and you can start or stop them whenever you want.
You retrieve events from log files by running EMS processes called distributors. You can initiate and terminate
distributors as dictated by your operations environment needs.