Writing Monitors for the Event Monitoring Service (December 1999)

12 Chapter1
Understanding the Event Monitoring Service
Event Monitoring Service Overview
The persistence client ensures that monitors that are running,
continue to run. If the persistence client detects that a monitor is not
running, it restarts the monitor. If the node reboots, the persistence
client restarts the monitors and reissues all monitoring requests.
Developers use the EMS API to create additional monitors for use
with client and TCP target applications, such as the EMS GUI or
ServiceGuard. Monitor components to be created include: resource
dictionary, resource monitor binary file, man page (recommended),
message catalog (recommended). Additional target applications can
also be written using the EMS API.
Figure 1-1 shows the relationships between the Event Monitoring
Service components.
Figure 1-1 Event Monitoring Service Components
The process is as follows:
1. The system administrator enters the client application, for example,
the EMS GUI or High Availability Clusters area of SAM, to
begin the discovery phase of creating a monitoring request.
The discovery phase, includes identifying the resources to be
monitored and configuring the request. It can be accomplished