Writing Monitors for the Event Monitoring Service (December 1999)
10 Chapter1
Understanding the Event Monitoring Service
Event Monitoring Service Overview
Event Monitoring Service Overview
The Event Monitoring Service (EMS) monitors system resources. Use
EMS to configure monitoring requests, check resource status, and send
notification when configured conditions are met. EMS monitors provide
instrumentation (knowledge about resources). EMS framework provides
registration and notification mechanisms.
EMS can work in a high availability environment. It can report a loss of
redundant resources. Identifying and reporting single points of failure
helps maintain a proactive approach to preventing the loss of data and
availability.
EMS only observes a system, and typically does not modify the system.
Use EMS with additional software to take or specify action unless your
monitor is designed to take corrective or recovery actions itself.
The three basic components of EMS are:
• Client and Target Applications
System administrators use client applications to set, modify, or
remove monitoring requests. System administrators use target
applications to receive event notifications and possibly take actions.
Client applications include ServiceGuard (MC/ServiceGuard or
ServiceGuard OPS Edition), the Event Monitoring Service (EMS)
GUI (Graphical User Interface), or other applications that interface
with the EMS API. ServiceGuard doubles as a target in that it
receives events and takes action.
The target application can be any application that supports the EMS
protocols. The supported protocols are:
— TCP/IP or UDP/IP
This includes any application that accepts these protocols and
follows the rules defined in the EMS Developer’s Kit.
— opcmsg method (for ITO)
This option is used for OpenView IT/Operations notifications.
— SNMP traps
This option can be used with any application that accepts SNMP