Service maps in New Relic One

Visualize dependencies quickly and easily across your environment with New Relic's improved service maps in New Relic One. Service maps help you see how all your entities work together across your system. Use service maps to troubleshoot problems, see how your environment works together, and ensure that issues don’t have downstream repercussions.

Service maps have some enhanced functionality that APM Service maps do not have, including:

A service map in New Relic One
one.newrelic.com > Entity explorer > (selected entity) > Service map: Service maps in New Relic One show your dependencies and how they're performing.

This feature is only available for Pro accounts.

Requirements

Service maps in New Relic One work with distributed tracing to connect relationships between entities. Service maps are still functional if you have not enabled distributed tracing, but we recommend having distributed tracing enabled for all agents. This ensures a more consistent experience while using service maps in New Relic One.

For best results, update existing agents to the latest version. The required minimum agent versions for maps are:

Minimum versions when distributed tracing is enabled

The required minimum agent versions for maps using distributed tracing are:

Minimum versions when distributed tracing is NOT enabled

The minimum version requirements for maps not using distributed tracing are:

Add or remove connections to an entity

To view service maps in New Relic One, from one.newrelic.com click on the entity explorer. Once you select an entity to view, you can select service maps from the sidebar.

The map shows your upstream and downstream services: entities toward the left are upstream, entities toward the right are downstream. To add or remove connections to an entity:

  1. Hover over the entity in the map that you want to alter.
  2. Click add or remove more connections.
  3. In the connection list, keep boxes checked for the entities that you want to appear in the map. Unchecked entities will be removed from the map.

Color coded for alerts

Each entity in a map displays a color dependent on its performance.

  • square Green: there are currently no violations for this entities performance.
  • square Yellow: there is an open warning violation for this entity.
  • square Red: there is an open critical violation for this entity.
  • square Gray: no alert conditions have been set for the entity
  • square-o White: agent not reporting. This means that the agent installed on the entity is not reporting any data. This is expected behavior for databases or externals.

Add maps and charts to dashboards

Add service maps to your dashboards
one.newrelic.com > Dashboards: adding a service map to a dashboard provides context for the data being reported and where it's coming from.

You can add any service map to a dashboard. For example, if you have a dashboard showcasing performance metrics for several entities, adding a service map to the dashboard shows how all the entities are related and provides additional context about your system.

To add a service map to a dashboard:

  1. Go to one.newrelic.com and select the Entity explorer.
  2. Select an entity from the index.
  3. Click on Service map.
  4. Click Add to dashboard. Search for the dashboard you want to add the map to.

Understand dependencies using API

You can discover the same relationship connections available in service maps with NerdGraph. For more information and examples, see the NerdGraph GraphiQL relationships API tutorial.

Externals and databases in maps

In the New Relic UI, your out-of-process services are referred to as web external or background external data. Externals and databases have slightly different features in service maps than other entity types:

  • Unlike other entities that appear in service maps, externals are aggregates. Clicking on an external service in the map shows you the list of all the external services that are rolled up into the one external entity. This is to reduce map clutter, as some entities can have dozens of externals being reported.
  • Databases are agentless. Because of this, alerts cannot be set for the database, as only see the service call is reported to New Relic.

Missing nodes

If you are unable to view certain entities in New Relic One service maps, see Troubleshooting: Missing or obfuscated data in New Relic One.

For more help

Recommendations for learning more: