Writing Monitors for the Event Monitoring Service (December 1999)

18 Chapter1
Understanding the Event Monitoring Service
Client and Target Applications
instance. An example of a full resource path for the physical volume
status of the device /dev/dsk/c0t1d2 belonging to volume group
vgDataBase, is /vg/vgDataBase/pv_pvlink/status/c0t1d2.
2. Specify when to collect value. Select either:
• When value is ...
If you are setting up a request for an asynchronous monitor, this is
the only option available.
• When value changes
• At each interval
Select this option to send an event periodically, regardless of the
value.
— When this option is selected, specify a polling interval for how
often the monitor checks the resource and reports the value.
Define a polling interval that is appropriate to your system
performance and reaction time needs.
3. Specify how often the monitor should check and send notification
about the resource:
the
• Initial option immediately checks and returns the resource
value regardless of threshold conditions.
• the Repeat option, which is the only applicable option for
asynchronous monitors, checks and returns the resource value at
each polling interval if threshold conditions have been met. State
type monitors can use the Repeat option in addition to the
Initial and Return options.
• the Return option checks and returns the resource value after a
threshold condition has been resolved and the threshold condition
is not longer true. This option applies to State type monitors.
4. Specify the notification protocols:
• opcmsg (IT/O), by severity or map severity from values
• TCP or UDP
• SNMP trap, by severity or map severity from value of event
• email