Manually create and send events

You can manually create and send events to confirm that Event Management properly manages events and generates alerts.

Before you begin

Role required: evt_mgmt_admin

About this task

For example, you can manually send events to:
  • Confirm that the MID Server is using a event connector definition and instance to send events.
  • Confirm that a event rules, event field mapping, and other configurations generate alerts.
  • Track an operation or action that did not generate an event.

Procedure

  1. Navigate to Event Management > All Events.
  2. Click New.
  3. Fill in the fields, as appropriate.
    Table 1. Parameters
    Name Description
    Source Event monitoring software that generated the event, such as SolarWinds or SCOM. This field has a maximum length of 100. It is formerly known as event_class.
    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.
    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.
    Resource Event unique identifier to identify multiple events that relate to the same alert. If this value is empty, it is generated from the Source, Node, Type, and Resource field values. This field has a maximum length of 1024.
    Source instance Name of the machine or software that generated the event. For example, SolarWinds on 10.22.33.44. Corresponding field display name is Source Instance.
    Message key Event unique identifier to identify multiple events that relate to the same alert. If this value is empty, it is generated from the Source, Node, Type, and Resource field values. This field has a maximum length of 1024.
    Severity The severity of the event. 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.
    • Clear: No action is required. An alert is not created from this event. Existing alerts are closed.
    • Info: An alert is created. The resource is still functional.
    Time of event Time that the event occurred in the source system. This field is a GlideDateTime field in UTC or GMT format. This field has a maximum length of 40.
    State The current processing state of the event:
    • Ready: Event has been received and is waiting to be processed.
    • Processed: Event was successfully processed.
    • Ignored: Value is not in use.
    • Error: Failure occurred while processing the event. For example, the event collection method or event Severity is blank.
    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.
    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.
    Additional information A JSON string that gives more information about the event. For example, {"evtComponent":"Microsoft-Windows-WindowsUpdateClient","evtMessage":"Installation Failure: Windows failed. Error 0x80070490"}. This information can be used for third-party integration or other post-alert processing. Values in the Additional information field of an Event that are not in JSON key/value format are normalized to JSON key/value format when the event is processed. For example, assume that the following plain text is in the Additional information field “Connection instance is successful”. When the event is processed, all this plain text becomes one JSON string and might not be useful within an alert. In the resultant alert, this string is in the Additional information field in JSON key/value format, containing the data: {“additional_content”: “Connection instance is successful"}.
  4. Click Submit.