Using the Event Monitoring Service (June 2003)

Understanding the Event Monitoring Service
Event Monitoring Service Overview
Chapter 114
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 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 in preventing the loss of data and
availability.
EMS only observes a system, and does not modify the system. Use EMS
with additional software to take or specify an action.
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 Extension for RAC), the Event Monitoring Service
(EMS) GUI (GraphicalUser Interface), theEvent Monitoring Service
(EMS) CLI (Command Line Interface), or other applications that
comply with the EMS API.
The target application can be any application thatsupports 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 IT/Operations notifications.
— SNMP traps
This option can be used with any application that accepts SNMP
traps, such as NNM or IT/O. You need to set up the application to
recognize the SNMP traps generated.
— email