Writing Monitors for the Event Monitoring Service (December 1999)

165
Glossary
A-K
asynchronous monitor A
monitor that monitors resource
instances (or resource classes)
asynchronously. It is event driven
and sends notifications when
events occur. It does not keep track
of the current state or value of
each resource it monitors.
client The application that sends
or cancels requests to monitor
particular resources. Examples of
this are MC/ServiceGuard, when it
starts a package, and the SAM
interface to EMS, when a user
creates a monitor request.
EMS Event Monitoring Service. A
set of APIs, together with the
Registrar process and the resource
dictionary, which allow client
applications to request that
resources be monitored and a
target application notified. The
Event Monitoring Service defines
the interface between resource
monitors and the client and target
applications.
EMS framework This is EMS.
See EMS.
ITO HP OpenView IT/Operations,
formerly known as Operations
Center.
L-Z
MC/ServiceGuard This is a
softwareproduct that allows auser
to customize and control resources
that are to be highly available. In
the event of a resource failure,
MC/ServiceGuardtransferscontrol
to back-up resources.
monitor request This is issued
by a client to request a resource
monitor to monitor a specific
resource instance.
notification A communication
from the resource monitor to the
target application that an event
has occurred during this polling
interval that meets the
user-configured criteria for
notification.
opcmsg A message which will be
interpreted by the ITO message
interceptor on the ITO managed
node and forwarded to the ITO
management server.
persistence client The process
that 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