We're still working on this feature, but we'd love for you to try it out!
This feature is currently provided as part of a preview program pursuant to our pre-release policies. The public preview includes access to Auto-Discovery and Transaction 360, bundled together. Having opted into the preview, you gain access to all three capabilities at no cost; opting out of the preview applies to all three as well.
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 other map experiences.
Service map vs. Maps
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.
Clustering
Not available
Automatically group nodes to declutter the map, making complex environments simple and manageable.
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, including bypass relationships, 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.
Maps is available only to the Advanced Compute customers. To enroll, navigate to one.newrelic.com > Administration > Preview & Trials, and enroll for New experiences: Maps, Transaction 360, and Auto-Discovery.
Map components
Get familiar with the components of Maps, which visualize the relationships within your services, resources, and teams, and show their health status.
The entity from which you open the map. It serves as the reference point for visualizing relationships with other entities one depth away.
Select the focal node to get the comprehensive view of the entity details on the right pane.
Connected nodes
The connected nodes are entities that have a direct relationship with the focal node. They appear one depth 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.
Select a node to get the comprehensive view of the entity details on the right panel. 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.
Zoom in, Zoom out, and Center and reset zoom
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.
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 directly from the staus summary.
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
Green: All nodes are operational
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.
Map 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, or dynamic data flows. This unified approach offers clear insights into service interactions, infrastructure dependencies, team operations, and data flows.
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, but you can choose to view associated infrastructure resources in a dedicated layer.
To access the map for mobile, browser, and APM environments:
To open the issue page, from Issues & Actitvity, select the issue that is associated with a service (Check the Entity name column).
To get the service map, from the issue page, scroll to the Impacted entries section.
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, you can also view the internal relationships between AWS services.
From the All entities page, select the host you want to view.
To open the map, on the host page, click Infrastructure.
To access the infrastructures associated with a service on the map:
From one.newrelic.com, open map for any service in APM & services, Mobile, or Browser.
To open the Dynamic Flow Map, point to a node and click Inspect infrastructure.
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 get the details of a team, from the Teams page, select the team.
Go to the Map tab.
The 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.
Important
Maps with Distributed tracing and Auto-Discovery 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
With the features and components of Maps, you can explore and manage your cloud environment in the following ways:
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.
Instrument the uninstrumented nodes
If there are any uninstrumented nodes in the map, they appear with a dotted border. After you instrument the nodes, the map refreshes to show the updated health status.
To instrument nodes:
From the health status summary of the map, point to Uninstrumented and click Instrument what's missing.
On the Add more instrumentation page, follow the on-screen instructions to instrument each entity.
Filter nodes by health status
If you want to focus on some nodes with specific health categories, filter the nodes as follows.
To open the Map View Settings panel, from the top-right of the map, click Settings.
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
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.
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
To organize nodes by a specific attribute in the map, go to the Group by drop-down and select the attribute.
To get the grouping on the map, click Apply. Each group displays the number of nodes it contains.
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
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: <account name>. 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
Green: All nodes are operational
You can 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.
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
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 depth away dependent nodes with connected edges.
Inspect infrastructure resources
To view the infrastructure resources associated with a node, point to the node and click Inspect Infrastructure. The infrastructure map opens, displaying the associated infrastructure nodes and their internal relationship two depths away from the APM service. If you have enabled for the Auto-Discovery feature, you can view the internal relationships between AWS services.
View dynamic 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.
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
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.
In Maps, gateways can mask the true entities that your focal node connects with. To visualize the actual node instead of the gateway, you can manually establish a bypass call relationship.
To set up a bypass call relationship:
On the map, select the gateway node that you want to bypass. The name of the gateways may start with, Gateway:, Nerdgraph:, or GraphQL:.
On the right panel, under the Tags section, add the service_gateway: true tag.
To apply the changes, refesh the map. The actual node replaces the gateway node, allowing you to view the bypass call relationship between the focal node and the actual node.
