Writing Monitors for the Event Monitoring Service (December 1999)

14 Chapter1
Understanding the Event Monitoring Service
Event Monitoring Service Overview
how to send event notification
A completed monitoring request identifies:
• what resources to monitor
• what events to watch for and how often
• what notifications to send when an event occurs
• where to send notifications
Events are defined for either of two resource state types:
• periodic checking against either thresholds or state/value changes
• continuous checking for asynchronous events
8. The registrar passes completed monitoring requests down to the
appropriate resource monitor application.
9. The monitor checks the resource, and other request information, as
specified in the monitor request. It passes back to the EMS API
whether the request is accepted or rejected and as appropriate, why a
request is rejected.
10.The EMS API provides the interface between the monitor and the
target.
11.The monitor begins collecting data as specified in the monitoring
request.
12.The EMS API interprets the information received from the monitor,
determines if an event occurred, and forwards the notification to the
target applications. The method of informing the target application of
a critical resource value can vary for different target applications.
In the case of ServiceGuard, the client application and the target
application are the same and reside on the same system.