EMS Manual

Standard Events
EMS Manual—426909-005
9-13
Object Name for Event Subject
A standard event type lets operators quickly identify the kind of events they need to
collect and process in their systems. Unlike event number, which lets management
applications take action on a specific object type, event type lets management
applications simply and efficiently process a group or class of events, regardless of
which subsystem or application the events came from.
For example, if a management application only needs to see events of certain types,
you can write a filter that only examines and forwards events of the needed type.
Without event type, the filter would have to examine SSID and event number for each
event and compare their contents to a list of needed values, a resource intensive and
error-prone operation, and you would need to change the filter whenever a new
subsystem or application is added to the system.
This section also specifies event types for some commonly reported information, like
trace, debug, or diagnostics information for problems in the production environment.
The content of these events is defined by the subsystems—the required common
tokens are defined here. These event types are specified by the User Content Type
token in the event message. This token is different from the Standard Content Type
token so these event messages can be migrated to standard events when the content
of such an event is standardized. Providing these event types (without the event
content) lets operators easily separate these subsystem-defined events from the
standard events.
Events that do not have the Standard Content Type and the User Content Type tokens
belong to the class of events defined prior to this standard. The content of these events
can only be interpreted using the event number and the SSID. Detailed knowledge of
the subsystem or application is required.
Object Name for Event Subject
Every event message has an event subject—the objects that the event is most
concerned with. Any object name included in an event subject:

Must not change before the object is deleted

Should uniquely identify the object from any point in the network
If this is not possible, the subsystem or application must identify the entity—for
example, the name of a manager process, a directory service or an algorithm—that
is needed to resolve the name in the network.

Should suggest the commands that can be used to control or inquire about the
object
Use the object type information associated with an object to suggest the command
set that applies to the object. The object type for an object is usually encoded with
the object name. Hence, subsystems and applications must ensure a unique object
type for an object.
For example, a subsystem could have an object token called BANK-TKN-
ATMNAME. The token name BANK-TKN-ATMNAME indicates the event subject is