--- title: Understand and use Maps source: https://docs.newrelic.com/docs/service-architecture-intelligence/maps/advanced-maps --- **Maps** provides a unified and integrated view of your cloud estate, allowing seamless navigation and exploration of services and infrastructure. It integrates tracing, infrastructure, and performance data into a cohesive experience, addressing limitations of the **[Service map](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/ui-data/service-maps/service-maps/)** experiences. - **Comprehensive visualization**: View your entire digital landscape that shows all your services and infrastructure in one place. This visualization helps you quickly grasp complex architectures and make informed decisions about your cloud environment. - **Automatic Resource Detection**: With [auto-discovery](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities/), Maps automatically identifies new resources and their relationships. This feature ensures your data is always current, reducing the time and effort needed to manually update and track changes in your cloud estate. ## Service map (old) vs. Maps [#differences] | Feature | Service map | Maps | | ------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | Focus | View one service at a time. | Gain a comprehensive view of multiple services, enhancing overall system understanding. | | Navigation | Navigate through individual services | Explore the entire cloud topology, including AWS resources, from a holistic view of the entities and their relationships. | | Grouping | Not available | Organize entities in multi-level grouping for simplified visualization and management. | | Infrastructure visibility | Limited context on infrastructure. | Directly inspect AWS and cloud resources, providing deeper insights into infrastructure support. | | Service relationships | See direct interactions between services. | Understand complex interactions for better dependency management. | | Health status summary | Basic health indicators | Filter services by health status to focus on critical, degraded, or uninstrumented services. | | Customization | Basic appearance settings | Tailor map view and edge styles to suit specific needs, improving clarity and focus. | ## Availability [#availability] Maps is available for all [Full platform users](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-type/#user-type-capabilities). On the [Data + Core Compute](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/) pricing model, all users are Full platform users and have access to Maps. Core and Basic users in a User pricing model continue to get the old maps experience. If you're a Full platform user and want to switch back to the old maps experience, click **Switch back for now** from the map view. ### Maps access across capabilities [#maps-access-capabilities] You can access Maps from various New Relic capabilities. Some capabilities provide Maps access by default, while others require enabling additional features through the [Feature Control Manager](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/feature-control-manager). | Capability | Pricing model | How to enable | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [APM](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-apm), [Mobile monitoring](https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/getting-started/introduction-new-relic-mobile), [Browser monitoring](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring), [Infrastructure monitoring](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring), [Workloads](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/workloads-overview), [Alerts](https://docs.newrelic.com/docs/alerts/overview), [Catalogs](https://docs.newrelic.com/docs/service-architecture-intelligence/catalogs/catalogs), [Teams](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/teams) | CCU (Core) | Available by default | | [Distributed tracing](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing) (Entity Map) | CCU (Core) | Available by default | | [Distributed tracing](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing) ([Dynamic Flow Map](https://docs.newrelic.com/docs/service-architecture-intelligence/maps/dynamic-flow-map)) | aCCU | Enable Transaction360 via [Feature Control Manager](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/feature-control-manager) | | [Transaction360](https://docs.newrelic.com/docs/apm/transactions/workload-performance-monitoring/transaction-workloads) ([Dynamic Flow Map](https://docs.newrelic.com/docs/service-architecture-intelligence/maps/dynamic-flow-map)) | aCCU | Enable Transaction360 via [Feature Control Manager](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/feature-control-manager) | ## Roles and permissions [#roles-permissions] Maps is a read-only experience. All [Full platform users](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-type/#user-type-capabilities) can access Maps without any additional roles. > #### ⚠️ IMPORTANT > > There are no create, update, or delete operations available within Maps. For more information on the overall SAI role model, refer to [SAI Getting Started](https://docs.newrelic.com/docs/service-architecture-intelligence/getting-started/#roles-permissions). ## Map components [#map-components] Get familiar with the components of **Maps**, which visualize the relationships within your services, resources, and teams, and show their health status. ![new-map-view](https://docs.newrelic.com/images/new-map-view.webp "new-map-view") **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > APM & Services**: Maps view. | Component | Description | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Focal node | The entity from which you open the map. It serves as the reference point for visualizing relationships with other entities one step away. To view comprehensive details about the entity, point to the focal node and select the info icon. | | Connected nodes | The connected nodes are entities that have a direct relationship with the focal node. They appear one step away from the focal node. - **Inbound nodes**: These nodes send data to the focal node and appear to the left and top of the focal node in the default view. - **Outbound nodes**: These nodes receive data from the focal node and appear to the right and bottom of the focal node in the default view. To view comprehensive details of a connected node, point to it and click the info icon. To open the map of that node, from the **Related entities** section in the right panel, click **See full map**. | | Edges | Edges illustrate the inbound and outbound relationships between nodes. Point to an edge to view the relationship type and the data flow direction. You can change the edge style from the **Map View Settings** panel by using the **Edge Path Type** drop-down. | | Legend | The legend, next to the zoom controls, lets you hide specific entity types you don't want to see on the map. | | Zoom controls | Adjust the map view by zooming in and out or centering and resetting the zoom level. If nodes are outside the main viewport, the map thumbnail provides a compact overview to help navigate and locate the nodes. As you zoom in, the map reveals more entity details. Entities with errors or anomalies stay labeled and visible at every zoom level. | | Health status summary | The Health status summary provides a quick overview of node statuses, using color-coded indicators and counts to help you identify areas requiring attention. You can [instrument uninstrumented nodes](#node-instrumentation) directly from the status summary. | | Service level availability (SLA) indicator | The SLA indicator appears if the availability percentage of the node drops below the SLA threshold. Pointing to the indicator displays the current availability percentage. To learn more about the SLA, refer to [Service level availability commitment](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/service-level-availability-commitment/). | | Clusters | Cluster is the logical grouping of nodes that simplify the map by consolidating related nodes. A cluster forms when at least 10 nodes: - Share the same parent node. - Have the same relationship type. - Belong to the same entity domain and type. - Exhibit the same dependencies (inbound or outbound). A cluster displays the number of nodes it contains, and the color of the cluster depends on the health status of the nodes within. - **Red**: At least one critical node - **Yellow**: At least one degraded node but no critical nodes Select a cluster to view the nodes in the right panel of the map. Reveal nodes from the panel to display them individually on the map outside the cluster. | ### Nodes [#nodes] Nodes represent all types of entities in the map. To visually distinguish between different types of nodes, and recognize their health status and SLA, the map uses the following icons: - Services, micro-services, and internal code - Data and integrations - External services - Mobile applications - Browser applications - Video player - Degraded node - Critical unknown node - Node with no alerts set up - Not reporting node - Uninstrumented node - Node with dropped SLA indicator ### Infrastructure nodes [#infra-nodes] To distinguish infrastructure nodes from service nodes, **Maps** uses the [**AWS Cloud Infrastructure**](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations/) icon set and color palette, since New Relic currently only supports AWS as a cloud provider for infrastructure entities on the map: - Analytics - AI/ML - Application and integration - Compute - Container - Database - IoT - Management and governance - Networking and CDN - Security - Simple Queue Service - Storage - Other ### Kubernetes nodes [#k8s-nodes] When you traverse a **Kubernetes** entity in the infrastructure map, **Maps** uses the following icons to represent Kubernetes resource types: - API server - Cluster - Deployment - Node - Pod - StatefulSet ## Visualize relationships [#visualize-relationships] **Maps** uses different visual patterns to represent relationships between entities, depending on the type of relationship. This keeps the map readable as your architecture grows: primary relationships stay visible on the canvas, while secondary details remain available on demand. To see these patterns applied to a specific trace, refer to [Understand the trace details UI page](https://docs.newrelic.com/docs/distributed-tracing/ui-data/trace-details/). **Line between two entities** A directed line with an arrow is the default way **Maps** represents a connection between two entities, showing the direction of data flow. For example, if Service A calls Service B, an arrow points from Service A to Service B. Most service-to-service relationships on the map use this pattern. **Boundary boxes** Some relationships represent containment rather than data flow. For example, a database cluster contains its instances, and a Kubernetes deployment contains pods. Representing containment with a directional line would incorrectly imply data flow where there is only structure. For entities with a **Contains** relationship, **Maps** automatically groups them inside a boundary box, with the parent entity visually wrapping its children. This shows the hierarchy without requiring you to read labels or follow arrows, and reduces the number of edges on the map. **Detail on the entity popover** Some relationships fan out too widely to draw as individual lines without cluttering the map. For example, multiple Kafka brokers can manage a single Kafka topic. Drawing a line to every broker would make the topic look more complex than it is. For these **Is managed by** relationships, point to the entity to view the full relationship detail in its popover, instead of adding permanent lines to the map. **Overlay icon** Some relationships are relevant but secondary, and apply to nearly every entity. For example, most services have a service level attached to them. Drawing a line from every service to its service level would dominate the map with edges. For these relationships, **Maps** shows a small overlay icon on the entity node instead of a line. The icon for a [service level](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/service-level-availability-commitment/) relationship appears only when that service level is alerting. Point to the icon to view the relationship details. ## Map entry points [#entry-points] **Maps** provides a consistent mapping experience accessible through various entry points. Depending on the type of entity you select to explore, separate views are available to show services, teams, infrastructure resources, entity relationships in a workload, or dynamic data flows. This unified approach offers clear insights into service interactions, infrastructure dependencies, team operations, and data flows. **Visualize service interactions** **Maps** enables you to visualize relationships and dependencies among services within mobile, browser, and APM environments. In its default view, the map displays only the services. Selecting a service node reveals its associated infrastructure resources in the bottom panel. To access the map for mobile, browser, and APM environments: 1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities)**. 2. From the capability list, select either **APM & services**, **Mobile**, or **Browser**. 3. From the service list, search and select the service you want to view. 4. To open the map, from the second-left nav, click **Service map**. To access the map for a service from an alert: 1. Go to **[one.newrelic.com > Alerts](https://one.newrelic.com/alerts)**. 2. To open the issue page, from **Issues & Activity**, select the issue that is associated with a service (Check the **Entity name** column). 3. To get the service map, from the issue page, scroll to the **Impacted entries** section. **Visualize infrastructure resources** Through **Maps** you can explore infrastructure resources and their internal relationships. It provides a detailed view of how infrastructure components support your services, enabling you to directly inspect AWS and cloud resources. The map helps you understand the underlying infrastructure dependencies that are critical for maintaining service performance and availability. With [AWS Auto-Discovery](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities), you can also view the internal relationships between AWS services. To access the Infrastructure map: 1. Go to **[one.newrelic.com](https://one.newrelic.com/alerts) > All entities**. 2. From the **All entities** page, select the host you want to view. 3. To open the map, on the host page, click **Infrastructure**. ![new-infra-map-view](https://docs.newrelic.com/images/new-map-infra-view.webp "new-infra-map-view") To access the infrastructure associated with entities on the map: 1. From **[one.newrelic.com](https://one.newrelic.com)**, open map for any service in **APM & services**, **Mobile**, **Browser**, or **Workloads**. 2. To open the **Infrastructure Map**, point to a node and click **Inspect infrastructure**. Or From the **Infrastructure** drop-down at the bottom of the map, select the nodes you want to inspect, and click **Apply**. The infrastructure map opens at the bottom of the map, displaying the associated infrastructure nodes and their internal relationships. **Visualize teams, their relationships, and owned services** Through **Maps** you can view team-specific services and their interactions. It allows you to explore services and dependencies within the context of your team's operations, facilitating collaboration and efficient management of team-owned resources. To access the Teams map: 1. Go to **[one.newrelic.com > Teams](https://one.newrelic.com/teams)**. 2. To get the details of a team, from the **Teams** page, select the team. 3. Go to the **Map** tab. **Visualize the dynamic data flow** The [**Dynamic Flow Map**](https://docs.newrelic.com/docs/service-architecture-intelligence/maps/dynamic-flow-map) offers a detailed view of data flow through your services, including interactions with databases and other backend components. It provides insights into performance and potential bottlenecks, allowing for effective troubleshooting. **Visualize the entity relationships in a workload** **Maps** illustrates the relationships and dependencies among entities within a workload, as well as between different workloads. They provide a comprehensive view of these relationships, including the health status, SLA, and data flow. Maps also depict hierarchical relationships when workloads are nested within one another. To access the workload map: 1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Workloads**. 2. From the **Workloads** page, select the workload you want to view. 3. To open the map, from the second-left nav, click **Maps**. To learn more about workloads, refer to [The workloads UI](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/) page. > #### ⚠️ IMPORTANT > > **Maps** with [**Distributed tracing**](https://docs.newrelic.com/docs/apm/distributed-tracing/getting-started/introduction-distributed-tracing) and [**Auto-Discovery**](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities) provides unified relationships between entities. While **Maps** remains functional even if you haven't enabled **Distributed tracing** or **Auto-Discovery**, enabling these features is recommended for a more impactful and consistent experience. ## Use **Maps** [#use-maps] With the features and components of **Maps**, you can explore and manage your cloud environment in the following ways: **Manage node visibility using health status** The Health status summary provides a quick overview of all nodes. Each health status is represented by a color legend, with a number next to each legend indicating the count of nodes in that status. This allows you to quickly assess and address areas needing attention. ![color-code](https://docs.newrelic.com/images/color-code.webp "color-code") > #### 💡 TIP > > In the **Map View Settings** panel, green represents operational nodes for health status filtering, and the green legend at the bottom-left of the map provides their count. However, on the map, operational nodes do not have a green dot, as this is considered the default state of a node. ### Instrument the uninstrumented nodes [#node-instrumentation] If there are any uninstrumented nodes in the map, they appear with a dotted border. To instrument a particular uninstrumented node, point to the node, click **Instrument**, and follow the on-screen instructions. You can also get the list of all uninstrumented nodes in the map and instrument them as follows: 1. From the health status summary of the map, point to **Uninstrumented** and click **Instrument what's missing**. 2. On the **Add more instrumentation** page, follow the on-screen instructions to instrument each entity. After you instrument the nodes, the map refreshes to show the updated health status. ### Filter nodes by health status [#node-filtering] If you want to focus on some nodes with specific health categories, filter the nodes as follows. 3. To open the **Map View Settings** panel, from the top-right of the map, click **Settings**. 4. From the **Health Status** list, select the specific status you want to view. The map view updates to show only the nodes with the selected health status. ### Manage clusters with health status [#cluster-health-status] If clusters are available in your map view, you can filter nodes in it by health status and display them separately. Point to a cluster and reveal the health status to show nodes with that status outside the cluster. This helps you focus on specific nodes within the cluster. **Group nodes to organize the map view** You can group nodes in the map to reduce clutter and highlight relationships, making it easier to identify patterns and manage dependencies. This structured approach provides a clear and organized view of your cloud environment, tailored to your specific needs. ### Create groups [#create-groups] 1. To organize nodes by a specific attribute in the map, go to the **Group by** drop-down and select the attribute. 2. To get the grouping on the map, click **Apply**. Each group displays the number of nodes it contains. 3. To add another level to the group, from the **Group by** drop-down, click **+ Create a group** > select an attribute > **Apply**. The first level attribute forms the primary group, and the second level attribute forms sub-groups nested in the primary group. You can apply up to five levels of grouping. #### Group appearance and naming [#group-appearance] Groups are named based on the selected attribute. For example, if you are grouping the nodes by the `Account` attribute, the group name appears as `Account: `. Groups are color-coded according to the health status of the nodes within them, as follows: - **Red**: At least one critical node - **Yellow**: At least one degraded node but no critical nodes Select a group to view the details of the grouped entities in a table at the right panel. You can also expand groups to view the nodes and nested sub-groups within them. As per your requirement you can reorder group levels by shuffling attributes in the **Group by** drop-down. **Navigate on the map to explore node details, relationships, and dependencies** **Maps** provides several features to help you explore relationships, dependencies, and metric and team details of an entity. When you point to a node on the map, a pop-over appears with the following interaction options, and three golden metrics. You can use these options to navigate and explore the map further. ### Expand dependency [#expand-dependency] To view the dependent nodes of any node on the map, point to the node and click **Expand dependencies**. That node becomes the focal node, revealing all one step away dependent nodes with connected edges. ### Inspect infrastructure resources [#inspect-resources] To view the infrastructure resources associated with a node, point to the node and click **Inspect Infrastructure**. The infrastructure map opens at the bottom of the map, displaying the associated infrastructure nodes and their internal relationship two steps away from the APM service. If you have enabled for the **[Auto-Discovery](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities)** feature, you can explore how AWS services connect internally. The map provides a hierarchical view that follows the order of resource organization: cloud > Region > VPC > Availability zone > Subnet > Auto-scaling group > Individual host. You can select a specific region or VPC to view the resources contained within it. ![infra-map](https://docs.newrelic.com/images/map-infra.webp "infra-map") ### View dynamic flow [#view-data-flow] To view the data flow through your node, including interactions with databases and other backend components, point to a node and click **View dynamic flow**. The dynamic flow map opens, providing a detailed view of data flow through the node, including interactions with databases and other backend components. For more details, refer [**Dynamic Flow Map**](https://docs.newrelic.com/docs/service-architecture-intelligence/maps/dynamic-flow-map). ### View node details [#view-node-details] To view the details of a node, point to the node and click the info icon. The comprehensive details of the node appear in the right panel. ### Access node owner [#access-node-owner] To access the owner of a node, point to the node and click the team name. The team page opens, displaying the team details and the entities owned by the team. ### Access the node details [#access-node-details] To view and adjust details of a node, point to the node and click the node name. The entity summary page opens, displaying the entity details.