logo

NJP

Event Management : Part 2 of Event Rules for CI Binding – Application/Database CI’s

My Knowledge Hub · Aug 04, 2021 · article

**INTRODUCTION**

This article is a continuation of my previous article where i explained about basic CI binding using event rules on hardware CI’s, in case if you guys have not see that then do see it with this link below:

### [Event Management : Part 1 of Event Rules for CI Binding – Hardware CI’s](https://community.servicenow.com/community?id=community%5Farticle&sys%5Fid=e768f551db3458906064eeb5ca96192d)

There we saw CI binding using Host name , IP address and Fetching the Node name from description and using it in node field to bind CI on alert. But as an organisation you need this CI binding to be as accurate as possible because this helps you to do proper impact analysis, facilitates good decision making and this helps ITSM process to route the tickets to proper groups, do root cause analysis. Also reporting is important aspect to see how many alerts where generated for this application and then divide them based on CI and CMDB Classes. This helps us to do Alert group which we will see in upcoming articles. So lets start with new use cases for CI binding but this time at Application Web Server levels and Database levels. To test this i will be using same Application Service as in previous article, also show below.

As shown above in RED we are going to focus on creation of alerts on 1 and 2\. This two are IIS Web Server and MYSQL database. To do this we have created new event rules which are shown in below sections with explanation and with videos i created for this articles.

We can override the CI binding using two options :

1. CI Identification
2. CI Field Mapping

Difference between this two is the first one uses CI identifiers rule to identify CI for binding it and second one uses the field value like name, ip address same as default binding. But the difference is you have to pass the database or application name in additional information field so that windows host relations will be checked for CI binding, this is explained below.

**USE CASE PDF IS ATTACHED TO THIS ARTICLE. ALL THE USE CASES ARE EXPLAINED IN DETAIL THERE, PLEASE GO THROUGH IT.**

YouTube Video links:

1.
2.

Please download the PDF from here :[ https://community.servicenow.com/community?id=community\_article&sys\_id=1c7eef84db095c10f7fca851ca961989](https://community.servicenow.com/community?id=community%5Farticle&sys%5Fid=1c7eef84db095c10f7fca851ca961989)

**Thanks and Regards,**
**Ashutosh Munot**

**[ServiceNow MVP 2019/2020](https://community.servicenow.com/community?id=community%5Fblog&sys%5Fid=fb488720dbaacc504819fb2439961900)**

**[My Article and Blogs](https://community.servicenow.com/community?id=community%5Fuser%5Fprofile&user=2a131665db1c1fc09c9ffb651f9619fb)**

**[YouTube Channel](https://www.youtube.com/channel/UCf7bnvR3MOiJN5tDxLZPNuw?view%5Fas=subscriber)**

View original source

https://ashutoshmunot.wordpress.com/2021/08/05/event-management-part-2-of-event-rules-for-ci-binding-application-database-cis/