Service Now Event Management CI Binding - Scenarios
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-
================================================================
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
https://www.servicenow.com/community/itom-articles/service-now-event-management-ci-binding-scenarios/ta-p/2319332