HP-UX Reference (11i v3 07/02) - 5 Miscellaneous Topics (vol 9)

e
EvmEvent(5) EvmEvent(5)
I18N message identification for the event.I18N message ID I18N_MSG_ID
Event format text. See the EvmEventFormat(3) and
evmtemplate (4) reference pages for a description of the
format string.
Format FORMAT
Reference to event explanation text.Reference REF
Event Name
The event name is the primary means of identifying an event. It must be present for an event to be posted.
Although it can be any syntactically valid string, the name should generally identify the posting facility and
indicate what happened.
The event name is an ASCII character string, made up of a dot-separated series of components, with the
left-most component representing the top of a notational hierarchy. Component substrings may include
any combination of letters, digits and underbar characters. There is no restriction on the number of com-
ponents that can be included in an event name. An event template must contain at least two components.
An event must contain at least three components to be accepted for posting.
The naming scheme provides an open-ended way to identify events, letting you provide detail to any level.
Careful naming gives the system administrator an intuitive and precise way to select events for viewing
and monitoring and facilitates the identification of the system components which issue events and the
recognition of patterns that warn of problems. The more detail included in the event name, the more pre-
cise the specification criteria can be.
Event Identifier
The event identifier data item is a numeric quantity, assigned to an event by the EVM daemon as the event
is posted. In combination with the host and timestamp data items, the value can be used to produce a
unique identity for an event.
The daemon assigns identifiers according to the following rules:
• Each posted event receives an unsigned integer event identification number, with a value greater by
one than that of the previous event posted through the same EVM daemon.
• The event identifier of the first event posted after the daemon is started or restarted is zero.
• The event identifier wraps back to zero after it has reached its maximum value.
• If a daemon receives an event that already contains an identifier, it does not generate a new identifier
for the event.
• New event identifiers are assigned only to events which the daemon validates and accepts for distribu-
tion.
• If an event is accepted and does not already contain an identifier, a new identifier is assigned to it
even if there are no subscribers for the event.
Event Priority
EVM uses an event’s priority value solely for filtering, sorting and presentation purposes - it does not use it
to prioritize the distribution sequence. The priority is an integer value in the range 0-700, with zero being
the least significant priority. This table indicates the event priority, the default action taken by evmlogger
for that priority, and a description of the priority.
EVM Default
Priority Name Notification Description
A dangerous situation has been detected and immediate
action either is required or has been taken.
700 Emergency Log, mail to root
A dangerous situation is imminent and immediate action
either is required or has been taken.
600 - 699 Alert Log, mail to root
A failure has been detected that renders some part of the
system inoperable.
500 - 599 Critical Log, mail to root
A noncritical failure has been detected in or by some com-
ponent of the system or application.
400 - 499 Error Log
HP-UX 11i Version 3: February 2007 − 2 − Hewlett-Packard Company 151