When tagging infrastructure CIs to application services, the app owner usually gives us a list of servers and databases to be tagged. Once the service recalculates, that app service often shows relationship to SQL instances and databases that we didn't tag and don't necessarily support the specific application. I'm trying to understand:
1) Regarding databases, what is the correct CI level to tag: database, database instance, or server?
2) Assuming we are tagging a shared server that runs an application AND happens to also host a SQL instance, how do we prevent that unrelated SQL instance from showing up as part of the application's map? If we tag the server, it's pulling in the SQL instance.
We have a traversal rule that I think MAY be contributing to the issue:
This is one of those things that might be best figured out by deactivating the rule in sub prod and seeing what happens. But I'm hoping someone else has already been through this and can help.
