EMS Manual

EMS Usage Best Practices and Recommendations
EMS Manual—426909-005
D-5
Event Frequency Guidelines
Event Frequency Guidelines
EMS-FRQ-101: Events should not be repeated if the same problem persists or the
same condition exists. See EMS-CON-121.
Event Specifications Guidelines
EMS-SPC-101: Your software specification should describe every event that your
software can generate, including:

Possible values and interpretations of all of its tokens (excluding the “infrastructure”
tokens added by the EMS subsystem itself, such as timestamps).

Whether each token is unconditional (always present in the event) or conditional
(only present sometimes).

Conditions in which a conditional event will be present.

All possible severities of the event in all possible conditions.

Emphasis token values.

Destination logs.

Operator text messages.

Cause (all conditions that can cause the event), effect (effect on the
application/service), and recovery (actions that can be taken to remedy the
situation described in the event).
Event Sustaining Guidelines
The intent of these guidelines is to keep events the same across different versions of
the software, so that applications and operators do not make incorrect decisions.
EMS-SUS-101: Events should not change in meaning. If an event is no longer relevant
or appropriate, it should not be generated. Instead, a new event with a new event
number should be defined.
EMS-SUS-111: Documented tokens in an event should not be deleted.
EMS-SUS-121: Event templates can be modified, but they should not be deleted.
EMS-SUS-131: The DDL definitions for tokens, token values, and events should not
change.