Service Map in #MSOMS automatically builds a common reference map of dependencies across your servers, processes, and third-party services. It discovers and maps all TCP dependencies, identifying surprise connections, remote third-party systems you depend on, and dependencies to traditional dark areas of your network such as Active Directory. Service Map discovers failed network connections that your managed systems are attempting to make, helping you identify potential server misconfiguration, service outages, and network issues.
OMS Service Map Overview of my Demo Environment
Machine Changes on HybridCloud01 Server
You now can see that the Previous Service State Running is changed in Stopped.
When you go more in details and look at the log Search in this event :
When this event is important to you you can make an OMS Alert on this Change :
With OMS Alert you can take actions like :
With Microsoft OMS Runbooks you can make Automation solutions for Hybrid IT Events.
Servicemap Server Properties
OMS Service Map Performance
OMS Service Map Updates
More information about using Awesome Service Map solution in Operations Management Suite (OMS) you can find here
Configuring Service Map solution in Operations Management Suite (OMS)
Service Map gets its data from the Microsoft Dependency Agent. The Dependency Agent is dependent on the OMS Agent for its connections to OMS. This means that a server must have the OMS Agent installed and configured first, and then the Dependency Agent can be installed. The following table describes the connected sources that are supported by the Service Map solution.
Operations Management Suite (OMS) SDK
I like Microsoft OMS Service Map a lot because you can see the relations between Servers, Services, Applications in a Hybrid IT environment and
get proactive alerts to take action to keep your Hybrid Datacenters Healthy