Using the Event Monitoring Service (June 2007)

Understanding the Event Monitoring Service
Event Monitoring Service Overview
Chapter 1 15
• monconfig utility
• resls or resdata commands
2. The EMS API provides the interface between the client request and
the registrar. There is a one to one correspondence between the client
and the registrar.
3. The registrar refers to the dictionary for a list of available resources
and related monitors.
The resources listed in the dictionary are passed back to the client.
4. When a discovery request is made that exceeds the scope of the
information in the dictionary, the registrar launches the appropriate
resource monitor application, if it is not already running, and passes
the request on to the monitor. Multiple registrars may access the
same monitor.
5. The EMS API provides the interface between the registrar and the
monitor.
6. The monitor identifies the resources. The list of resources is passed
back through the registrar to the client requestor.
7. The system administrator, through the client application:
• Continues to drill down through the list of available resources
supplied by the registrar, dictionary, and monitor
• Identifies the resources to monitor
• Completes the monitoring request, defines conditions of where
and how to send the 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 stateless events