Other resources

Release Notes

Video Tutorial

Map overview

With Map, you can identify the components of your applications and services, and view relationships between the applications and the endpoints on which they are running. With this knowledge, you can make your applications more resilient and know the impact before taking endpoints down for maintenance.

Application dependency mapping

In Map, a business application is a logical grouping of software, devices, and network traffic. You can create an application map to show a visual representation of the dependencies between these components.

For example, you might have a three-tier web application that consists of a database server, web service, and other software. A set of clients access this application over the network. By defining the components of this application, you can visualize which servers run the application code and which endpoints are accessing the application. You can change the map to include or exclude servers or end-user computers. As a result, you might find that a critical part of the application is running on an endpoint that is not maintained as a server, or that unexpected clients are trying to access the application.

Endpoint mapping

With an endpoint map, you can create a map that consists of a set of IP addresses. By viewing details in an endpoint map, you can see the processes that are running on specific endpoints and the business applications that depend on a specific endpoint.

Application resiliency

By identifying application dependencies, endpoints, infrastructure, and utilization, you can better identify single points of failure, capacity planning problems, and inefficient use of IT.

If a specific endpoint needs maintenance, for example, you can understand all of the applications that outage might affect.

To investigate an outage, you can create multiple maps from different time periods and compare them to determine what changed.