Writing Monitors for the Event Monitoring Service (December 1999)

Chapter 1 11
Understanding the Event Monitoring Service
Event Monitoring Service Overview
traps, such as OpenView NNM or IT/O. You need to set up the
application to recognize the SNMP traps generated.
— email
This option does not require any extra handling. Specify the email
address when the monitoring request is created.
— syslog and textlog
This option does not require any extra handling. Specify the log
file when the monitoring request is created. Syslog and textlog
notifications go to the local system.
— console
This option does not require any extra handling. Specify the
console when the monitoring request is created. Notifications go to
the local system.
— ServiceGuard
This option requires that the client and target application both be
ServiceGuard running on the same local system. EMS and the
monitors need to be on each node in the cluster where the
ServiceGuard package can run.
• Resource Monitors
Resource monitors observe designated resources and report back
resource values or events to the Event Monitoring Service.
Hewlett-Packard provides numerous monitors such as the:
— EMS High Availability Monitors, which include the HA Database
Monitor, HA Disk Monitor, HA Cluster Monitor, HA Network
Interface Monitor, and HA System Resource Monitor.
— A variety of EMS Hardware monitors
— A variety of product specific monitors such as ATM and OSI
• Event Monitoring Service Framework
The EMS Framework provides the interface between the client
applications, monitors, and target applications.
The EMS Framework contains the Applications Programmers
Interface (API), registrar, and the Resource Dictionary. Additional
processes include the persistence client.