Using the Event Monitoring Service (November 1999)

Chapter 1 15

Understanding the Event Monitoring Service

Event Monitoring Service Overview

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 identiﬁes 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

• identiﬁes the resources to monitor

• completes the monitoring request deﬁnes conditions of where and

how to send event notiﬁcation

A completed monitoring request identiﬁes:

• what resources to monitor

• what events to watch for and how often

• what notiﬁcations to send when an event occurs

• where to send notiﬁcations

Events are deﬁned for either of two resource state types:

• periodic checking against either thresholds or state/value changes

• continuous checking for asynchronous stateless events

8. The registrar passes completed monitoring requests down to the

appropriate resource monitor application.

9. The monitor checks the resource as speciﬁed 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 speciﬁed in the monitoring