Writing Monitors for the Event Monitoring Service (December 1999)

Chapter 3 77
Creating a Resource Monitor
Defining the Resource Dictionary Hierarchy
• Resource monitor lanmond:
All resources under /net/interfaces/lan/status are controlled by
the lanmond resource monitor. All subclasses and resource instances
beneath the /net/interfaces/lan/status level are dynamic.
• Resource monitor mibmond:
The mibmond resources are explicitly defined. This allows you to
specifically define resource criteria. The resources under
/system/jobQueue1Min, /system/jobQueue5Min, and
/system/jobQueue15Min are controlled by the mibmond.
• Resource class /system/filesystem:
The filesystem resources reference to a class of resources, not a
monitor. fsmond controls dynamic resources under
/system/filesystem/avail/Mb, for example /home and /var.
Other classes can be added. A /system/filesystem entry defines a
higher level class.
• Resource monitor fsmond:
All resources under /system/filesystem/availMb are controlled by
the fsmond resource monitor. The resources referenced here are
subclass to the filesystem resources in /system/filesystem entry.
Naming Hierarchy
The following is the resource naming structure described in the
/etc/opt/resmon/dictionary/DEFAULT file. Check the contents of that
file to find the latest naming structure, and to find the best resource class
to use to name your resources.
/adapter
/event
/status
/applications
/db
/user-defined
/connectivity
/events
/hubs
/multiplexors
/switches
/status