HP-UX Event ManagerAdministrator's Guide

Configuring Event Manager
Configuring Event Manager Logger
Chapter 3 69
# Don't forward mail events through mail
/* This line establishes filtering for the events. As with an
event log definition, the filter string specifies the set of
events that are handled by this forwarder. To prevent an
event loop from occurring if the mailer posts high-priority
events, signifying a possible problem in the mail subsystem,
mail events are explicitly excluded from this forwarder
. */
filter "[prio >= 600] & ![name @SYS_VP@.syslog.mail]"
/* These lines suppress multiple forwarding of events. The
suppression mechanism for a forwarder is similar to that for
an event log. Here, the purpose is to prevent the command
from being sent multiple times in a short period because of
the same event being posted repeatedly. In the example, a
particular event is forwarded once every two hours at most.
*/
suppress
{ filter "[name *]"
period 120 # minutes
threshold 1 # No. of duplicates before suppression
}
# This evmshow command writes a subject line as the first
# line of output, followed by a detailed display of the
# contents of the event.
# The resulting message is distributed by mail(1).
/* This line defines the command that executes when an event is
handled by the forwarder. The event is piped into the
command's stdin stream. The result of this command is shown
in the comments preceding the command line. */
command "evmshow -d -t 'Subject: EVM ALERT [@priority]: @@' |
mail root"
# Limit the number of events that can be queued for this
# command:
maxqueue 100
}
# Secondary configuration files can be placed in the following
# directory. See the evmlogger.conf(5) reference page for
# information about secondary configuration files.
configdir /var/evm/adm/config/logger
If you make any changes to the logger configuration file, you must run
the evmreload command to inform the changes to the logger. For more
information about the evmreload command, see evmreload (1M).