• /
  • Log in
  • Free account

How to use service maps

Here is information about how to use the current service maps feature. For help using the earlier service maps feature, see Legacy APM service maps.

Service maps helps you visualize dependencies quickly and easily across your environment. They help you see how all your entities work together across your system. You can use service maps to troubleshoot problems, see how your environment works together, and ensure that issues don’t have downstream repercussions.

Service maps also supports cross-account access so help you see relationships between entities for all your accounts.


Service maps 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.

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

Add or remove connections to an entity

To view service maps, from one.newrelic.com click 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.

  • Green: there are currently no violations for this entities performance.
  • Yellow: there is an open warning violation for this entity.
  • Red: there is an open critical violation for this entity.
  • Gray: no alert conditions have been set for the entity
  • 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.

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.

Create issueEdit page
Copyright © 2022 New Relic Inc.