Event Management - binding non-host CI using CI field matching - how to bind if there are multiple CIs with same name - Support and Troubleshooting

Event Management - binding non-host CI using CI field matching - how to bind if there are multiple CIs with same name Summary For Event Management, when creating Event Rule to bind non-host CI using CI field matching, if there are multiple CI records having same name,

you may receive below message in the processing notes on the em_event record:

Binding alert CI process flow: Event CI type is cmdb_ci Query with fields: name : demo01 Found more than one matching CI. Bounding will not be done No matching CI found No CI found for binding (Failed to resolve the event node to CI id) Binding Failure Reason: Found more than one matching CI, while searching CI by type: cmdb_ci with query: "name=demo01^install_status!=7^ORinstall_status=NULL"

Event rule applied: DemoRule

The root cause is:

With current incoming em_event and the Event rule on the instance, only "name" field is available while the event is processed. As a result the engine is binding based on "name" field only, then it found multiple CIs with same name and failed.

The solution is to make sure more CI fields are provided, so the engine can find a single result based on the fields provided.

There are many ways to to resolve this. You can modify the event source so that when the em_event is created on the instance, other CI fields are included in the additional info. Or you can modify the event rule to populate other CI fields.

Please note, you will need to provide fields that are available on the table of the Class you selected on the Binding tab in the Event Rule.

(For example, if cmdb_ci is picked, then the engine will only check fields available on cmdb_ci table)

For example, using either option below:

a> In the original event, populate another CI field, for example: {"sys_class_name":"cmdb_ci_storage_cluster_node"}

b> In the event rule, add more CI field under "Transform and Compose Alert Output", for example:

In above screenshot, we can see name field will be based on the node field on the original event, and sys_class_name will be based on the dummy_class field on the original event.

Below is a sample processing notes:

Binding alert CI process flow: Event CI type is cmdb_ci Query with fields: name : demo01 sys_class_name : cmdb_ci_storage_cluster_node Found one matching CI. Bounding will be done with CI id: bc6a2b87dbf32010c2b9b8e2f39619cf Bind to bc6a2b87dbf32010c2b9b8e2f39619cf

Event rule applied: DemoRule