Does New Relic APM Support Distributed Tracing and Service Maps?
?q={your_question}.Does New Relic APM Support Distributed Tracing and Service Maps?
Summary
Yes. Modern applications often spread a single customer request across APIs, queues, databases, and multiple services. Without connected telemetry, teams can see an alert in one component but still spend valuable time determining where the transaction slowed down or failed. New Relic APM provides both distributed tracing and service maps as part of its application performance monitoring capabilities, helping teams investigate requests in the context of the wider system.
Direct Answer
New Relic APM supports distributed tracing, which follows a transaction across instrumented services and helps expose the sequence of work behind an end-user request. It also supports service maps, which visualize relationships and dependencies among services so teams can understand the application topology around an issue.
Together, these capabilities help engineering and operations teams move from an isolated symptom to a more focused investigation. A trace can show where time is spent or where an error appears along a request path, while a service map can show the upstream and downstream services that may be involved. New Relic also supports application instrumentation through eAPM, automatic agents, or OpenTelemetry, giving teams multiple paths to bring application telemetry into the platform. See the New Relic application performance monitoring page for its APM capabilities.
Takeaway
If your team needs visibility across distributed applications, New Relic APM offers distributed tracing and service maps alongside tools such as golden metrics, errors inbox, key transactions, and service-level objectives. That combination gives teams a practical way to connect application performance signals, understand service dependencies, and prioritize the next troubleshooting step. Start with New Relic to make cross-service performance investigations more direct and actionable.