Service maps are visual, customizable representations of your architecture. Maps automatically show your app's connections and dependencies, including applications, databases, hosts, servers, and out-of-process services. (In the New Relic UI, your out-of-process services are referred to as web external or background external data.) Health indicators and performance metrics show you the current operational status for every part of your architecture.
Service maps help you:
- Understand how apps and services in your architecture connect and talk to each other.
- Quickly see the current health and operational state of your entire environment.
- Troubleshoot operational issues and understand the impact of problems down to the host and instance level.
- Collaborate and drive shared understanding of an architecture.
Access to this feature depends on your paid subscription level.
Access service maps
To access service maps:
|If you're in...||To view maps||Learn more|
|New Relic One||Go to one.newrelic.com > Entity explorer > (select an entity) > Service map.||Service maps in New Relic One give you increased access to all the entities across your accounts, and help you understand how your entire environment is connected.|
|New Relic APM||Go to rpm.newrelic.com/apm > Service maps.||Service maps in APM let you create, customize, and share maps related to an individual app.|
Identify operational issues
Maps are color-coded to provide a quick look at the current status of your environment. Select nodes on a map to view additional performance metrics, and a full list and health check of each node's connections. The map automatically connects nodes into the map, so you can see which apps on the map talk to which.
You can use service maps to troubleshoot and assess the impact of a performance problem between a calling application and a specific database.
Understand your entire environment with New Relic One
With service maps in New Relic One, you can view your service and its status in the context of its up and downstream dependencies. Use maps in New Relic One to identify the root cause when troubleshooting an incident.
Use New Relic One service maps to:
- View all your entities without any setup: most entities in New Relic One are automatically connected to their dependencies in service maps.
- Read connections between entities via API with the GraphQL relationships API.
- View entities all across your organization's accounts.
- Add a map to a dashboard.
For a full description of these maps, see service maps in New Relic One.
Understand your application architecture in APM
APM service maps are great for:
- Closely monitored app or service (the app that your New Relic account users are most interested in)
- Central app or service (app with a lot of connections)
- Highest traffic app or service (app with highest throughput)
For a full description of these maps, see APM service maps
Once you have an app node on the map, you can begin to add its connections to the map, including New Relic Browser apps, databases, or external services (for example, third-party APIs). Every node you add is automatically connected into the map, so you can see the shape of your app's architecture emerge.