Upstream and Downstream relationships while using Service mapping

[Nik Amy]

Hi,

We are using Service mapping. Its creating lot number of upstream and downstream relationships on a CI.

Say, if I open a linux server it has got around 12 webspheres under downstream.

Its confusing users when they look at the form. They say only 1 such websphere should ideally appear.

How to avoid that.

[tompowe]

It might be because you have Traffic-based mapping and so it's finding more connections than it normally would

[Nik Amy]

Hi Tom,

Yes I have turned on traffic based mapping. I read that the tool uses AI to create only the needed CI's/Relationships,  but its creating so many unwanted CI relationships.

Also without traffic based turned on, the maps are hardly building the maps.

/Nik

[tompowe]

Lots of Service Mapping needs to be modified.  Traffic-based is to give you an idea of what is talking to each other, but the goal is to modify the patterns to pick up only the needed connections.  You need to look at the patterns being fired, and read through them to understand what they are trying to do.  They look for configuration files where they can get the information needed to create a connection.  Your environment is probably different than out of the box, so you will need to modify the patterns to find the correct config files and grab the right information.

[Nik Amy]

Yes you are right, thanks!

By the way is there a way to remove those unwanted CI relationships build based on Traffic based discovery. How to identify them exclusively and delete them.