Bind alerts to a specific device

  • Release version: Yokohama
  • Updated June 16, 2026
  • 2 minutes to read
  • Bind each alert directly to the originating device to establish a clear source of impact. This ensures accurate troubleshooting, reduces noise from unrelated alerts, and helps teams focus on resolving the right issue faster.

    Before you begin

    Role required: evt_mgmt_admin

    About this task

    In IT environments, multiple devices like switches have many smaller components, such as ports. When something goes wrong, it's not enough to just say the switch has an issue—the system needs to pinpoint exactly which port is causing it. Binding alerts to the specific port that triggered the issue allows teams to act faster and fix the real issue without wasting time checking the entire switch or unrelated components.

    The following example procedure shows the alert binding configuration for a switch named IP-Switch-1, ensuring alerts target the correct port. The event rule setup starts by enabling the Override default binding option and selecting CI field matching as the Binding type. Choosing Switchport as the CI type instructs the system to bind alerts to individual ports. The Binding Device Map defines how the system links the switch (cmdb_ci_ip_switch) to its ports (dscy_switchport) using the cmdb_ci reference field. This map guides the binding logic. Under Configuration > Network > Switches, selecting IP-Switch-1 reveals its switchports and interface names. When an incoming event includes a matching interface name in the Additional information field, the system binds the alert directly to the correct port—ensuring precise and meaningful alert context.

    Procedure

    1. Navigate to All > Event Management > Rules > Event Rules.
    2. Select New.
      List of event rules
    3. Select the Binding tab.
    4. Select the Override default binding check box.
    5. In the Binding type field, select CI field matching.
    6. In the CI type field, select Switchport.
      The CI type determines the specific CMDB table where the system searches for the matching CI.

      Binding and CI type

    7. Navigate to All and search em_binding_device_map.list.
      The Binding Device Maps page opens. Here the column values From ci type is mapped to To ci type using the Mapped column. For example, cmdb_ci_ip_switch is mapped to the Switchport [dscy_switchport] table using the reference field cmdb_ci.
      Binding device maps
    8. Navigate to All and search switches and select Configuration > Network > Switches.
      The IP Switches page opens.
      IP switches page
    9. Select IP-Switch-1 to view the details page.
    10. Select the Switchports tab.
    11. Navigate to All > Event Management > All Events.
    12. Select the event with Node value as IP-Switch-1.
      Additional information field of the event
      In the following image, you can see the processing notes indicating that the binding has occurred between the alert and the matching device.
      Processing Notes of the event