Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Alert binding to CIs with event rules

Log in to subscribe to topics and get notified when content changes.

Alert binding to CIs with event rules

When alerts are associated with CIs, the task of remediation is simplified. During alert generation, Event Management uses event rules and other mechanisms to automatically bind alerts to CI information from the CMDB. For tracking purposes and remediation, the alert shows information about the CI that caused the event.

Alert binding process flow

Alerts bind to CIs based on the following process flow:
  1. When an event arrives, Event Management checks the node or CI identifiers.
  2. If no node exists, the generated alert can bind to the CI using the alert Type, Additional information, or Configuration item identifier fields.
  3. If the event has a node value, search for a valid host.
  4. If the event has a host and a CI type, try to bind to a device CI.
  5. If the event has a host, try to bind to the application CI.
Figure 1. How alerts bind to CIs

The event can contain the binding process flow in its Processing Notes field.

Tracking and remediation

Alerts can be bound to CIs from the CMDB for tracking purposes and remediation. Event Management uses event rules and various mechanisms to automatically bind CIs to alerts. When information from an event populates a field with a value, the value either originates from the event source or from event rules. This enhances remediation, functionality, and integration with other ITOM products.

Binding to an application running on a specific host

If the event is specific to an application type, use the following steps to bind alerts to a specific application:
  • Use the procedures in the topic.
  • Create an event rule with a filter that captures events on the application type you want.
  • In the event rule, select Binding. Event Management binding
  • Click Override default binding.
  • In the Binding Type field, select either CI's Identification or CI field matching.
    • For CI's Identification, specify the Class. Event Management binding
      • In the Criterion attributes field, specify name and sys_class_name.

        Event Management binding

      • In the name Add Value field, specify the required name.
      • In the Container level 1 area, specify the required values.
      • If further container level fields appear, specify the required values.
    • For CI field matching, specify the required CI Type.
  • In the binding process, after the host is found, the algorithm matches all additional_info attributes that have the same name as CI fields for that CI type. If the match is successful, the event is bound to the CI.
  • If more than one matching application is found on the host, the alert is bound to the host and not to the application.
Where there is no CI Type, for example, if you want to bind alerts to a SQL server application when the CPU on sqlServer.exe is over 90%, instead use these procedures:
  • Populate the Node field in the event with the CI name, FQDN, IP, or MAC address value. The bind is successful even if host has more than one IP address or MAC address.
  • If you want to use a unique identifier that is not one of the four mentioned above, populate the event rule CI Identifier (ci2metric_id) field with one or more unique identifiers of the CI. This field should be in JSON format. For example, to use a unique identifier that is not one of the four mentioned above, add a CI Identifier (ci2metric_id) filter field with one or more unique identifiers of the CI. If the host CI is VMWare VM, and it has a field called MOID, use the JSON format and specify: {"moid":"<CI moid>"}
  • Create an event rule with an event match field which maps the process name to the mapping variable sa_process_name. In this case, do not use the CI type.

Binding procedures

Use the procedures in these topics to bind alerts.
Feedback