Writing Monitors for the Event Monitoring Service (December 1999)

62 Chapter3
Creating a Resource Monitor
Writing the Monitor
— Subclass events refer to “Processing a Subclass Request Event.”
— Monitor request events refer to “Processing a Monitor Request
Event.”
— Resource update events refer to “Processing a Resource Update
Event.”
— Unregister events refer to “Processing an Unregister Event.”
— Terminate events refer to “Processing a Terminate Event.”
— Asynchronous notifications refer to “Processing an Asynchronous
Notification.”
— Internal timeouts refer to “Defining an Internal Timeout.”
• rm_monitor_stop()
This is a required function.
NOTE The SAM interface to EMS provides a Show Instance Description
button. What is displayed when this button is selected is pulled from the
Subclass replies RmDescription text. Use this area to provide useful
information to the users. For example, describe or explain the resource,
include resource parameters, values, recommended thresholds, and
references to the .dict file and man page. The newline (\n) character is
allowed in this description block.
Man Page Recommendations
When you write the man page for your monitor, include:
• Options. Standard man page information to enable users to make
informed modifications to the resource dictionary file.
• Description of the resources being monitored. Identify the State for
each resource
• List of files. Reference the executable, dictionary, and any log files you
have created.
• Minimum polling that your monitor supports if your monitor is a
State monitor that supports polling.