Notification

Indicates if this event has been acknowledged

The time in epoch milliseconds, when this Notification was acknowledged. A time of ‘0’ means that the Notification has not been acknowledged

Indicates if this event is ACTIVE currently

Category of this event. The event category represents a broad categorization of the event, e.g. availability vs. performance.

The certainty of this event

Display name for the event class.

Class name of the object where this event occurred. This attribute along with InstanceName and EventName uniquely identify this event

Indicates if this event should be cleared when it is acknowledged. Set this to TRUE only for events that do not expire nor have sources that generate a clear

Uniqe key of notification across domains

Type of device on which notifiation occured

The string shown in the UI when this Event’s name is displayed.

The class name of the topology element associated with the event in the repository where this event resides. This may or may not have the same value as ClassName

The name of the topology element associated with the event in the repository where this event resides. This may or may not have the same value as InstanceName. The string is empty if there is no related element.

Display name for the event Name.

Name of the event. This attribute along with ClassName and InstanceName uniquely identify this event.

The current state of this event. ACTIVE: The event is currently active. WAS_ACTIVE: The event was active, but we lost contact with the event source. INACTIVE: The event is inactive. UNINITIALIZED: The event has not been notified yet; the object does not yet represent a notified event.

The textual representation or description of the event

Indicates the nature of the event. A MOMENTARY event has no duration. An authentication failure is a good example. A DURABLE event has a period during which the event is active and after which the event is no longer active. An example of a durable event is a link failure

First event notification time in epoch milliseconds

Does this notification causes other notifiations

A quantification of the impact of this event on the infrastructure and/or business processes. There are no pre-defined semantics to the value of this attribute other than a larger numeric value indicates a larger impact

Did this event occur during maintenance?

Display name for the event instance

Instance name of the object where this event occurred. This attribute along with ClassName and EventName uniquely identify this event.

Notification is live or historical

A notification is a problem when all of the original event types are ‘PROBLEM’ or ‘UNKNOWN’. There must be at least one ‘PROBLEM’, i.e. ‘UNKNOWN’ by itself is not a problem

Indicates if this event is a root cause event

Time in epoch milliseconds of last event change

Last clear time in epoch milliseconds

Last notification time in epoch milliseconds

Name of Event

Notification state object.

The number of occurrences of this event starting from FirstNotifiedAt until LastNotifiedAt

The name of the user that is responsible for handling this event

ID assigned in case the event is part of polling batch from the underlying source.

State assigned to differentiate, if the event is part of polling batch or subscription

Timestamp in epoch milliseconds when the event from the underlying source was processed.

“An enumerated value that describes the severity of the event from the notifier’s point of view: 1 - Critical is used to indicate action is needed NOW and the scope is broad, e.g. an outage to a critical resource. 2 - Major is used to indicate action is needed NOW. 3 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 4 - Unknown indicates that the element is unreachable, disconnected or in an otherwise unknown state. 5 - Normal is used when an event is purely informational.”

The name(s) of the domain(s)or domainGroups that have originally diagnosed and notified - directly or indirectly - current occurrences of this event. If there are more than one original domain, the attribute lists each separated by a comma. When the notification is cleared, the last clearing domain stays in the value.

The name(s) of the domain(s)or domainGroups that have originally diagnosed and notified - directly or indirectly - current occurrences of this event. If there are more than one original domain, the attribute lists each separated by a comma. When the notification is cleared, the last clearing domain stays in the value.

The type(s) of the events(s), i.e. ‘PROBLEM’, ‘EVENT’, ‘AGGREGATE’ in the source domains that have notified current occurrences of this event. If there is more than one domain the attribute lists each separated by a comma, in the same order as SourceDomainName.

This table maps an original source to corresponding immediate sources.It also maintains domain groups corresponding to immediate sources.

This indicates additional information related to the events source

Place holder for data related to other tools

Trouble ticket ID

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

User defined field

Internal notification id

JSON Object or HashMap with flexible key value pairs of type String, that represents the tag names and its corresponding values