Writing Monitors for the Event Monitoring Service (December 1999)

20 Chapter1
Understanding the Event Monitoring Service
Resource Monitors
Resource Monitors
Resource monitors are applications written to gather and report
information about specific resources on the system.
The resource monitor:
• Provides a list of resources that can be monitored
• Provides information about the resources
• Monitors the resources it supports
• Provides values or events to the EMS API notification
The EMS framework evaluates the data. Routines determine if any
clients have registered interest in this event. If so, an event has
occurred, and the EMS API sends notification in the appropriate
format to the configured target(s).
Monitors can be either:
• queried for status—they keep track of the current status or can
readily obtain it.
These are polled monitors. They can also detect events
asynchronously if designed for it.
• event driven—asynchronous notification only and cannot be queried.
These do not track current states and only know the status of the last
event.
Installing Resource Monitors
To obtain additional information about installed monitors:
1. Go to the /etc/opt/resmon/dictionary directory.
Each monitor registered with EMS has a dictionary file that is stored
in this directory.
2. View the monitor dictionary file.
Each dictionary file name is descriptive of its monitor. The file
extension is typically .dict. For example, the mibmonitor dictionary
filename is mibmond.dict.