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: When an event arrives, Event Management checks the node or CI identifiers. If no node exists, the generated alert can bind to the CI using the alert Type, Additional information, or Configuration item identifier fields. If the event has a node value, search for a valid host. If the event has a host and a CI type, try to bind to a device CI. 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. Alert binding proceduresAlerts 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.Bind alerts to a host CIYou can create an event rule to bind alerts to host CIs. An incoming event from a host CI can bind to an alert based on the event Node field value. If the value resides in a different event field, you can use an event rule transform to copy the data to the Node field on the alert.Bind alerts to a specific host CIYou can create an event rule to bind alerts to the correct device CI. An incoming event from a device CI can bind to an alert based on event rule transform information. However, first identify the host CI that the device is running on.Bind alerts for non-host CIsAn incoming event from a discovered business service, manual service, or alert group can bind to an alert based on an event rule and the corresponding event field mapping. The event field mapping requires a URL or the port number and corresponding IP address for each service or alert group.Bind alerts for application CIsAn incoming event from an application CI can bind to an alert based on event rule transform information. Create an event rule to bind alerts to the host CI and also to the application CI. Trigger alerting bind to a CIYou can manually bind an alert to a CI by triggering a new alert.View CIs that have alert bindingEvent Management uses the Event Management - Node Count job to show CIs that have alert bindings. This information is stored in the Licensed Usage [em_unique_nodes] table.