- My View
We have few CIs which are created manually in the CMDB CI table. When we get any events for these CIs, the Configuration Item on alert or incident is not populated.
The node name in the event is same as the CI name in CMDB.
What could be the potential issue and how to get this working. Any help would be appreciated.
In Alert can you see Configuration Item.
Yes. I can see that field, but not filled automatically.
So You can write a business rule in which before insert you can take node value and set Configuration Item Value.
I want it picked up from the CMDB as it happens for the other CIs within CMDB.
Then you need to debug, How your alerts are getting created and the mapping between them.
What is the CI type of the CI you created? Also is there another CI with the same name?
If you have two CIs with the same name but of different types, you may be facing ambiguous resolution problem. Creating an event rule for binding should resolve such scenario.
What would also be helpful is to check the event processing notes. Here is an example of a failure:
In both cases the node was an actual FQDN (like HOSTNAME.DOMAIN.COM) but in the first example we did not have a CI with the same hostname or FQDN as a name and the resolution failed. In your case (as you explained) you do have an existing CI with the proper name, but you should still check the processing notes for clues regarding why the binding failed.
You may want to check this topic in the documentation. It explains the CI binding flow and in the "Alert binding procedures" topic under it you can see the best practices with some examples. Please note that the links I posted are for Jakarta. Make sure to select the applicable release.
I hope this helps.
Do It Wise
Don't do it twice.