HP-UX Event ManagerAdministrator's Guide

Using Event Manager
Logging and Forwarding Events
Chapter 2 51
Logging and Forwarding Events
The response to an event is any action determined by your site-specific
needs and conditions. This response can range from activating alarms or
paging responsible personnel, to making a log entry or ignoring an
expected occurrence of a regular activity.
You can configure the event processing sequence to perform a series of
dependent tasks, by using an event output by one task as the trigger to
activate the next process. Event Manager provides an interface to the
response activity through the logging facility. The available options are
event storage and event forwarding.
The logger, evmlogger, started automatically by the Event Manager
daemon, is responsible for the following:
• Displaying selected events on the system console or other devices
If a terminal device is indicated as the logfile in the configuration
file, all events meeting the filter specifications of an eventlog
statement are formatted for display on the terminal. For more
information about the configuration file, see “Configuring Event
Manager Logger” on page 67
• Storing selected events in one or more log files
• Forwarding selected events to interested parties in some other form
By default, the logger handles events posted through its local daemon.
For more information, see “Event Manager Command Line Utilities” on
page 20.
The logger is an ordinary client that is controlled through a configuration
file. The default is the /etc/evmlogger.conf file, described in
“Configuring Event Manager Logger” on page 67. For more information
on this file and command, see evmlogger.conf (4) and evmlogger (1M)
manpage.
Logging Events
All events meeting the specifications of an eventlog group in the
configuration file are written to the event log. For the default location of
this file and the naming conventions, see “Event Manager System Files”
on page 23 .