EMS Manual

EMS Usage Best Practices and Recommendations

EMS Manual—426909-005

D-3

Event Destination Guidelines

There are two primary event destinations: your EMS Collector and $0. The following

guidelines should be used in deciding where the events should be reported:

EMS-DST-101: Events should never to logged to $ZLOG (the OSM Collector). This

collector is reserved for events from NonStop subsystems.

EMS-DST-111: In general, avoid using $0 (the Primary Collector). Most HP System

events go into that log. Events that are important to your Operations staff can be

logged to $0.

EMS-DST-121: Most, if not all, of your events should be logged to your own EMS

Collector.

Event Subject Guidelines

EMS-SUB-101: Event subject token should identify the real object for which the event

is reported.

Examples: Service name in a service down event, device name in a device needs

service event.

EMS-SUB-111: Event subject token should NOT be a generic process name or

program file, etc., unless the event corresponds to that process or program file itself; it

should be the object/resource managed by that process.

Example: An alarm created event by an application should have as the subject token

the object on which the alarm is created, rather than the application process that

created the alarm.

EMS-SUB-121: Multiple event subject tokens should be used if one of them is not

sufficient to indicate the object for which the event is reported.

Event Severity Guidelines

EMS-SEV-101: All non-informational events should use the ZEMS-TKN-ISO-

SEVERITY token to indicate the severity of the event.