Difference between Service Mapping and CI Dependency View

[kuroiwa]

Service Mapping allows you to throw an API to a service endpoint and check the server/DB relationship from the　endpoint from the service origin.

CI's Dependency View is one of the information obtained from Discovery.
(e.g., the relationship between server, disk, software, etc.)
　
(1) Information association is based on the assumption that each CI is Discovery, and the path is ascertained from the log?

(2) Is the above understanding of the difference between service mapping and dependency view correct?

Thank you in advance.

[Rahul Priyadars · Accepted solution]

Horizontal Discovery is one of nice to have Pre-Req of Service Mapping.

Horizontal Discovery runs on a given IP range and scan interconnected components - provided Credentials are configured.

In Service Mapping you traverse one URL/Entry Point from Top to Bottom - Scanning Applications, Middleware , DB and Infra etc. 

So Service Maps covers full view of one of the applications while plain CI view represents the connected components for given CIs and dependencies.

Regards

RP

[suvro]

Dependency view is based on records in cmdb_rel_ci and it is about relationship between CIs

But in Service Mapping it is mostly focused on Business Services. It makes a map of all associated CIs which are supporting the Business Services. It takes into account what dependency view takes into account + communications happening with the CIs (which port is commincating with which servers) +standard  patterns defined as per standard architecture + traffic based connections.

[Community Alums]

There are already couple of nice answers, but I'll try to add my 2 cents here:

Service Mapping is more like a logical map (+real one though) of the CIs while  dependency view shows "real" connections between the CIs. Try to imagine it that way - in addition to the answers above 🙂