Non-host CI Binding in the Event Rules

[Shantanu1]

Hi Experts!

I am trying to create an Event rule for AWS SNS Alerts.

This is include creating Event Rules & the Alert Management rules to run a flow to create INCs.

I am attempting the use the "Cloud Service Account" CI in the INC, and for this I am using a Non-host CI binding as show below, but the Alerts is not getting mapped to the same CI. In the Event I see that the binding is sucessfull. Any suggestions on this would be highly appreciated!

Binding alert CI process flow:
Event CI type is cmdb_ci_cloud_service_account
Query with fields:
account_id : XXXXX
Found one matching CI. Bounding will be done with CI id: XXX
Bind to XXX

Event rule applied: AWS SNS Events

[Henrik Jutterst]

Hi there @Shantanu1 maybe I can help you.

Can you share the Binding stage in the Event Rule to show what you've done?

Here's a random binding from an OOB event Rule:

And also. How is the INC created? Do you have your own Alert Management Rule for these cases that's triggering in this case? Do you need to update the SubFlow to use the Configuratino Item in the Create Task stage in the Flow?

[Shantanu1]

Hey @Henrik Jutterst 

Thanks for the reply!

Below is a snippet of the Binding I have done in the Event Rule;

In the Event record, I can see that binding has been done, but the Alert doesnt have a Node or CI in it

I have Alert Management rule that is triggering a sub flow to get the INC created.

[Henrik Jutterst]

Is it possible for you to show what the Event looks like and what is in the node field?

You sent the processing notes and based on that it looks like it's binding to the correct CI, or am I wrong?

"Found one matching CI. Bounding will be done with CI id: XXX
Bind to XXX"

[Shantanu1]

You are right, in the event processing Nodes I can see that the binding is successful.

In the Event, The Node field has to be cleared out as to allow Non-host CI binding, here my binding step

The issue is in the Alert record. I can see the Node & CI fields both are empty on the alert created. The INC created as a CI of Class"next hop routing rule" that is completely irrelevant 🙂

Below is my event record: