EMS Manual

EMS Manual426909-005
D-1
D EMS Usage Best Practices and
Recommendations
Introduction
EMS (Event Management System) is a key component in the management of HP
NonStop Systems. It is used by HP NonStop subsystems to create, manage, and
display events that are used in the management of the software and hardware
components of NonStop Systems. It is also used by third parties and customers in the
management of their software and hardware components.
This document contains the best practices and recommendations when designing and
implementing EMS events. It is highly recommended that you consider these
guidelines so that your software makes efficient and effective use of EMS.
Event Requirements Guidelines
EMS-REQ-101: Create a documentation that describes what events are reported and
how they will be used. This information will be useful to the audience in dealing with
the events.
Considerations: The following should be considered when formulating EMS
requirements.
Who is the audience for the events?
Operator: Is it a human operator (e.g, data center operator)?
Application: Are any of the events processed by an application and result in
automated actions (e.g., an email message)?
Internal versus External Consumption: Are the events meant for your
organization’s internal usage or for your customers?
How will the events be used?
How will the operator or application use the events? Include the usage scenarios.
Event Content Guidelines
EMS-CON-101: An event should report a significant change in system or application
condition. Examples of such changes are:
Conditions that require an operator action; e.g., process stop.
State changes of significant objects (devices, services, etc.); e.g., ATM needs
service, application server down.