Example: Bind alerts to CIs using dynamic CI types
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Event Management
Use event field mapping to dynamically bind alerts to the appropriate CIs based on event attributes, eliminating the need for separate event rules for each CI. This approach simplifies configuration, improves accuracy, and enhances alert binding.
Before you begin
Role required: evt_mgmt_admin
About this task
In general, for an event generated from a specific source mentioned in the Source field, the system applies the corresponding event rule. The override default binding option in an event rule specifies a specific CI class for binding. However, in a more dynamic use case, the CI class is not predefined and can change based on event attributes. For example, suppose a customer has multiple CIs with the same name, but each CI belongs to a different CI class. In the traditional event rule method, as the CI class (or the CMDB table) is defined for a CI, the mapping is incorrect because the system searches in the same CI class for all CIs with the same name and attributes, instead of looking in the specific CMDB table defined for each CI class.
To resolve this—in other words, to determine the correct CI class to search—the system uses the CI type field from the event to identify the CI class. By using an event field mapping that maps from event attributes to CI type, it becomes possible to know which CMDB table to search, ensuring that the CI is correctly mapped to the event.
Procedure