Bind alerts to a specific device
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 , 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.