Service Now Event Management CI Binding - Scenarios

[Rahul Priyadars]

Recently i started working on Service Now Event Management and found Event node to CI binding as interesting one. An incoming event from a host CI can bind to an alert based on the event Node field value. Just wanted to share some of the examples which may help others.

Postman Rest GUI is used to submit events to Service Now Event Management.

User Case 1- Populate the Node field in the event with the CI name ( CI belongs to cmdb_ci_hpux_server  class which is inherited from cmdb_ci_hardware ).

Sample JSON Used in Postman for event Submission.

Event Created at Service Now event Management Table.

\

Event Rule Applied , Alert Created and Alert is coupled with actual host ci of CMDB which is hpux1.

User Case 2- Populate the Node field in the event with the FQDN Name ( CI belongs to cmdb_ci_hpux_server  class which is inherited from cmdb_ci_hardware ). FQDN is an attribute of the CMDB CI Class.

Sample JSON Used in Postman for event Submission.

Event Created at Service Now event Management Table corresponding to above event.

Event Rule Applied , Alert Created and Alert is coupled with actual host CI of CMDB which is hpux1.

User Case 3- Populate the Node field in the event with the IP Address ( CI belongs to cmdb_ci_hpux_server  class which is inherited from cmdb_ci_hardware ). IP Address is an attribute of the CMDB  CI Class.

Sample JSON Used in Postman for event Submission.

Event Created at Service Now event Management Table corresponding to above event.

Event Rule Applied , Alert Created and Alert is coupled with actual host CI of CMDB which is hpux1.

User Case 4- Populate the Node field in the event with the Mac Address Of Device ( CI belongs to cmdb_ci_hpux_server  class which is inherited from cmdb_ci_hardware ). IP Address is an attribute of the CMDB  CI Class.Make Sure a relationship exists between the server CI and Network Adapter CI. Populate Mac Address in Network Adapter CI attribute.

Sample JSON Used in Postman for event Submission.

Event Created at Service Now event Management Table corresponding to above event.

Event Rule Applied , Alert Created and Alert is coupled with actual host CI of CMDB which is hpux1.

In All above use cases We see same event rule is applied and it used service now default Binding. Details on default binding is more available on service now wiki- 

https://docs.servicenow.com/bundle/orlando-it-operations-management/page/product/event-management/re...

================================================================

User Case 5- Populate the Node field in the event with the Device CI . In this case CI belongs to File System Class (cmdb_ci_file_system) And we want to bind File System CI in Alert and ITSM Incidents/Change Requests. Event Rule uses CI Identifier to bind with file system CMDB CI.

Sample JSON Used in Postman for event Submission.

Event Created at Service Now event Management Table corresponding to above event

Event Rule Applied , Alert Created and Alert is coupled with actual host CI of CMDB which is fsname1.

In this example i am also showing you the CI identifier used in Event Rule.

User Case 6- Populate the Node field in the event with the Application CI . In this case CI belongs to Application Class (cmdb_ci_appl) And we want to bind Application  CI in Alert and ITSM Incidents/Change Requests. Event Rule uses CI Identifier to bind application CI in CMDB.

Sample JSON Used in Postman for event Submission.

Event Created at Service Now event Management Table corresponding to above event.

Event Rule Applied , Alert Created and Alert is coupled with actual host CI of CMDB which is Bapp1.

In this example i am also showing you the CI identifier used in Event Rule.

I just tried to demonstrate the concept of CI Binding of Service Now Event Management at one place. There are many scenario like binding with Db Instance , IIS , Apache which you can try. 

With this i am concluding this article.

!! Happy Learning !!

Regards

Rahul Priyadarshy

[Sumit Pandey1]

Good to learn, thanks for sharing!

[shwetanksingh]

Great info...collectively together..thanks a lot Rahul !!!

[kumarsatyam]

Nice explanation of CI binding. Link of docs only provided theoretical aspect but the way you explained is phenomenal. 

Thanks rahul for this article it will definately help to SNOW associates.

[Community Alums]

Enjoyed reading the article above; really explains everything about CI binding in detail.

The article is very interesting and effective. Thank you for sharing this on community forum.

[Durga Prasad R1]

Nice article Rahul.

[jain25rajesh]

This is really awesome article Rahul, Very well explained,This help in understanding the complete CI binding.

I tried reading multiple blogs to understand the Ci binding but couldn't understood all scenarios. This article does cover all scenarios and are real time and working well for me also.

Thank you so much!!

[Ashish38]

This article has cover all scenario of CI binding. Good to learn.

[Community Alums]

This helps in understanding the complete CI binding. Thanks for sharing such content.

[Rahul Priyadars]

thanks

[Juhi Batra1]

With the help of screenshots, it become easier to understand. Thanks a lot for creating such an explanatory article

[Rahul Priyadars]

thanks  for valuable inputs.

[Aanchal1]

Thanks Rahul for explaining the CI binding scenarios. Article is very interesting and self explanatory. 

Thanks for sharing the article. 

[Rahul Priyadars]

thanks for the input

[Anindya Bhattac]

Any pointers or articles for non-host binding ? the documentation is not clear enough. I working on alerts from kubernetes services . source is google monitor 

[pratiksha5]

Hi Rahul I am not able to see the screenshots. am I missing something? PFA

[Sives]

Thanks Rahul , Good information!!!!

I'm working on Event Management,  CI's are not binding based on MAC Address.

In Event rule ci binding given as below

Transform and compose tab

Above rule is working for few MAC Address and updating the CI in alert, though Mac Address not not in network adapter table.  It is not working for few Mac Address and giving below error in event

In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_hardware]. Add these input values in payload item '{"className":"cmdb_ci_netgear","values":{"mac_address":"XX:XX:XX:XX:XX:XX"},"internal_id":"XXXXaed7e2d582XXXXXX","sys_object_source_info":{},"settings":{},"sys_ire_info":{},"display_values":{}}'.

Is there any mistake in event rule? 

Thanks in advance for any suggestions!!!

[Community Alums]

Hi @Rahul Priyadars ,

I am working on event managenet, one of my customers is asking for below,

Suppose application service is running on XYZ linux server then, we will get only XYZ linux server name in node of event form and want to bind it automatically to application service.

Means they are not sending that application service anywhere in event details, they want to bind the application service as CI running on XYZ linux server.

I checked this is not possible, we need to get some details of application service(name, identity) to bind the alert to application service CI.

Can you please share your thoughts on this OR will confirm whether is it achievable or not.