Database CIs Service Mapping

[Srinivas Cheer1]

We are in the process of converting our Business Services into Calculated Application Services, but encountering with the following challenge.

• When we made DB Instance relationship to a Calculated Application Service; Server & all Databases(Catalogs) which are related to that Instance is populating under CI association table (hope this is expected as Databases are child of DB Instance).

Now the concern here is, only few Databases are related to that particular Application Service(1), the other Databases are related to some other Application Service(2) which we don't want to show in the Application Service(1).

Any thoughts how do you handle this scenario?

Example:

1. DB Instance1 is running on Server1
2. Databases A,B,C,X,Y&Z are contained by DB Instance1
3. Databases A,B&C are belongs to AppService1
4. Databases X,Y&Z are belongs to AppService2

When we made relationship for AppService1 with DB Instance1 (Appl) by using Depends On:: Used By type - Server1 & all Databases A,B,C,X,Y&Z are listing under CI Association table or on the Service Map. We don't to show X,Y& Z Databases which are related to AppService2.

Thanks.,

[Rahul Priyadars]

This is a know behavior in case an Instance have databases pointing to 2 different applications.

I have seen similar scenario post in past also.

See if you can do using dependency maps filters/controls.

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/business-service-management-map-ng/reference/r_NGBSMMenus.html

Regards

RP

[Johannes]

We are facing the same issue.

In my mind, the logical thing is that the "database" is dependent on the "database instances" to be able to run, and having the relationship in this direction would allow for different "applications"/application services" being dependent on different "databases" running on the same "database instance".

However, when running discovery OOTB, the "databases" are getting upstream relationships to the "database instances", i.e. the relationship "path" will be: from "server" up to "database instance" down to "database" up to "application"/"application service". 

Our application teams needs to be aware if there is an issue with a server where the database runs, if there are patching activities on the servers etc., but I believe this will not work the way the relations are created OOTB.

Or is there something I do not understand?