Event Management tracks individual events to manage external systems. An event is a notification from one or more monitoring tools that indicate that something of interest has occurred, such as a log message, warning, or error. Event Management receives or pulls events from one or more external event sources and stores them in the Event [em_event] table. Event Management provides a list of raw incoming events.

1. Navigate to Event Management > All Events.
   The All Events list displays the following columns.

   Table 1. All Events list

   Column	Description	Populated by
   Time of event	The time that the event occurred, in the network node time zone.	External event monitoring tool
   Source	Event monitoring software that generated the event, such as SolarWinds or SCOM. This field has a maximum length of 100 digits.	External event monitoring tool
   Description	Reason for event generation. Shows extra details about an issue. For example, a server stack trace or details from a monitoring tool. This field has a maximum length of 4000 digits.	External event monitoring tool
   Node	Node name, fully qualified domain name (FQDN), IP address, or MAC address that is associated with the event, such as IBM-ASSET. This field has a maximum length of 100 digits.	External event monitoring tool
   Type	Pre-defined event type, such as high CPU, which is used to identify an event record. This field has a maximum length of 100 digits.	External event monitoring tool
   Resource	Node resource that is relevant to the event. For example, Disk C, CPU-1, the name of a process, or service. This field has a maximum length of 100 digits.	External event monitoring tool
   Message Key	Unique event identifier to identify multiple events that relate to the same alert. If this value is empty, it is generated from the Source, Node, Type, Resource, and Metric Name field values. This field has a maximum length of 1024 digits.	External event monitoring tool
   State	The status of the event: Ready: Event has been received and is waiting to be processed. Queued: Event is queued by the event processor job. Processed: Event was successfully processed. Error: Failure occurred while processing the event. For example, the event collection method or event Severity is blank. Ignored: Value is not in use.	Event
   Severity	Mandatory. The options are typically interpreted as follows: Critical: Immediate action is required. The resource is either not functional or critical problems are imminent. Major: Major functionality is severely impaired or performance has degraded. Minor: Partial, non-critical loss of functionality or performance degradation occurred. Warning: Attention is required, even though the resource is still functional. Info: An alert is created. The resource is still functional. Clear: No action is required. An alert is not created from this event. Existing alerts are closed.	Event
   Alert	If an alert was created as a result of the event, this field contains the unique ID that Event Management generates to identify the alert.	A matching event rule or event field mapping

2. To review a single event, click the required row in the Time of event column.
3. To review the event rules that processed the event, in the Related Links section click Check process of event.
   For further ways to see which event rules were applied to the event, in the Events list, you can optionally select to display the Event rule and Processing Notes fields.

   

   Table 2. Optional event fields to display the applied event rule

   Column	Description
   Matching Event rule	Contains the event rule that matches the current event rule definitions. This information is primarily used to create event rule recommendations for events that currently are not covered by rules. If event rules have been modified, this information can be retrieved from the Processing Notes field, described below. Note: This field does not show the history of event rules that were applied to the event.
   Processing Notes	View information related to the binding to CI type and the event rules that were applied to the event.

4. To create an event rule if an event is not associated with an event rule:
   1. Click the required event. The event opens in the Event form.
      
   2. Click Create Event Rule.
      The fields of the new Event rule are populated with data from the event. You can use the event information, for example, when composing fields for alerts.