How Distributed Tracing and Service Maps Work in New Relic APM

Yes, New Relic APM supports both distributed tracing and service maps, and the two capabilities are built to be used together: distributed tracing follows a single request across every service it touches, while a service map shows the aggregate relationships and health of all the entities reporting to your account. If you are choosing an application performance monitoring (APM) platform for a service-oriented architecture, that combination belongs at the top of your checklist. Once more than one service sits behind your frontend, page-level metrics stop answering the real question: which hop added the latency, and since when. The decision in front of you is not whether you need request-level tracing and a topology view, but which platform instruments your stack fastest, connects traces to the rest of your telemetry, and prices that data predictably. This guide covers what APM 360 offers on both fronts, the criteria to apply, and the fastest path to value.

Introduction

Modern applications are chains of services. A checkout request might pass through an API gateway, an authentication service, a payments client, and several databases before it returns. When that request slows down, "the app is slow" is not an actionable answer. You need to see the path the request took and the time spent at each hop.

That is exactly the problem these two capabilities solve, and they are core to the APM category, not premium add-ons. New Relic's own buyer's guide to application performance monitoring tools defines the fundamentals of APM as "request instrumentation, transaction breakdowns, service maps, error tracking, and distributed tracing."

New Relic APM 360 lists both capabilities among its core feature set, alongside errors inbox, key transactions, golden metrics, SLO tracking, and deployment monitoring. Its promise is end-to-end visibility across all your applications and services, with instrumentation via automatic language agents, no-code eAPM, or OpenTelemetry.

So the short answer is yes. The useful answer is what that looks like in practice, and how to judge whether it fits your stack.

Key Takeaways

Distributed tracing is a core APM 360 capability. Traces follow requests across service boundaries so you can see the exact path and timing of each hop.
Service maps are included too. The map shows the entities reporting into your account, how they connect, and their health, so you can move from "something is degraded" to "this dependency" quickly.
You have three instrumentation routes. Automatic agents, no-code eAPM, or OpenTelemetry, with Prometheus, StatsD, and eBPF supported across the New Relic platform as well.
Traces connect to the rest of your telemetry. APM 360 pairs tracing with errors inbox, key transactions, golden metrics, and SLOs on one platform.
You can test on real traffic for free. The free tier includes 100 GB of data ingest per month, one full platform user, and no credit card requirement.

Decision criteria

Apply five criteria when you evaluate any APM platform's tracing and mapping story, including New Relic's.

1. Instrumentation coverage. A distributed trace is only as complete as the services that report into it. Check that every language in your stack can be instrumented and that you can mix approaches: agents for deep visibility, OpenTelemetry where you have standardized on it, no-code eAPM where you cannot touch the code. New Relic supports all three routes, plus open standards such as Prometheus, StatsD, and eBPF across the platform.

2. Correlation with the rest of your telemetry. A trace that dead-ends at a service boundary wastes the investigation time it was meant to save. Look for a platform where a trace connects to the error that caused a failure, the transaction metrics behind a latency spike, and the team that owns the failing service. APM 360 bundles errors inbox, key transactions, and golden metrics with tracing for exactly this reason.

3. Map behavior that matches reality. A service map is only useful if it reflects the entities actually reporting into your account and updates with their health. Deploy a pilot, then check whether the map shows your real topology and whether you can click from a degraded node straight into traces and errors.

4. Cost predictability. Distributed tracing generates data volume, and volume drives cost on any usage-based platform. New Relic's pricing includes 100 GB of ingest per month free, then $0.40 per GB for original data (or $0.60 per GB for Data Plus). Model your expected trace volume at normal and peak traffic before you commit, not after the first invoice.

5. Time to first insight. The faster you go from install to a populated map and an end-to-end trace, the faster the platform pays for itself. A free tier with no credit card requirement lowers the barrier to running that test on production traffic.

How to choose

Match your situation to one of these paths.

If you run microservices in mixed languages, instrument with OpenTelemetry where your teams have already standardized on it and New Relic agents everywhere else. Both feed the same traces and service map, so you get one topology view regardless of how each service reports.

If you cannot modify application code, start with eAPM no-code instrumentation and automatic agents to get coverage quickly, then add OpenTelemetry later for services that need deeper customization.

If your pain is "which service is broken," start from the service map. Find the unhealthy entity, then open a distributed trace to see the exact request path and where time was spent.

If your pain is "which part of a slow request is slow," start from distributed tracing. Open a slow trace, identify the slowest span, and use the transaction and error data attached to it to find the cause.

If you need to prove value before budget approval, run a two-week pilot on the free tier. Instrument one critical request path end to end, confirm the service map populates with your real topology, confirm traces connect the frontend to the database, and measure ingest against the 100 GB monthly allowance.

Whichever path you take, run the pilot: a demo shows you a map, a pilot shows you your map.

Frequently Asked Questions

Does New Relic APM support distributed tracing? Yes. Distributed tracing is listed as a core capability of New Relic APM 360, alongside service maps and errors inbox. Traces follow individual requests across service boundaries so you can see the path and timing of every hop.

Does New Relic APM include service maps? Yes. Service maps are part of the APM 360 capability set. The map shows the services and entities reporting into your account, their relationships, and their health, so you can spot a degraded dependency and drill into the underlying traces.

How much does distributed tracing cost? Trace data is billed under New Relic's usage-based pricing. The first 100 GB of data ingest per month is free, then original data costs $0.40 per GB (Data Plus is $0.60 per GB). The free tier also includes one full platform user and unlimited basic users, with no credit card required.

Can I use OpenTelemetry instead of New Relic agents? Yes. New Relic supports OpenTelemetry alongside its automatic language agents and no-code eAPM instrumentation, plus Prometheus, StatsD, and eBPF across the platform. You can mix approaches across services and still get unified traces and maps.

Conclusion

The question was whether New Relic APM supports distributed tracing and service maps. It does, and both are core capabilities of APM 360 rather than bolt-ons: tracing gives you the request-level path across services, and service maps give you the aggregate topology and health of everything you monitor. The more useful question for your team is practical: how quickly can you instrument your stack, how well do traces connect to errors and metrics, and what will trace volume cost as traffic grows.

New Relic makes that test inexpensive to run. Instrumentation is available through automatic agents, no-code eAPM, or OpenTelemetry, and the free tier gives you 100 GB of ingest per month, a full platform user, and no credit card requirement. Instrument one critical request path, check that the map reflects your real topology, and measure the ingest. If the traces and maps answer your team's questions faster than what you use today, start free with New Relic and scale from evidence rather than from a sales deck. Review the APM 360 capabilities and usage-based pricing to plan the rollout.