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.
In Map, an application service is a logical grouping of software, devices, and network traffic. You can create an application service map to show a visual representation of the dependencies between these components over the past 24 hours.
For example, you might have a three-tier web application that consists of a web server, an application server, and a database. A set of clients access this application over the network. With Map, you can visualize the application components, servers that host components, and clients that are accessing the web application.
With an endpoint map, you can create a map of the processes and dependencies on a specific IP address. You can see the processes that are running on specific endpoint, understand what connections those processes are making, and see the application services that depend on the endpoint.
By identifying application dependencies, endpoints, infrastructure, and architecture, 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.
Last updated: 7/2/2020 10:52 AM | Feedback