New Relic
APM & Distributed Tracing
Auto-instrument services to get golden signals and end-to-end traces.
New Relic APM drops a language agent into your application (Java, .NET, Node, Python, Go, Ruby, PHP) that auto-instruments common frameworks, web servers, and datastore clients. Out of the box you get the golden signals per service — throughput, response time, and error rate — plus transaction traces, database query analysis, and an automatically built service map showing dependencies.
A fitness tracker for each service that records every move automatically, plus a shared GPS trail showing the whole relay race so you can see which runner lost the time.
Key Concepts
1
Distributed tracing connects those per-service views into the full request path. The agent propagates a trace context across HTTP and messaging boundaries, so a trace stitches spans from every service a request touched, with a flame-graph-style waterfall to localise the slow or failing hop. Errors are grouped into the errors inbox, and because traces and metrics share NRDB, you can pivot from an Apdex/latency chart to the exact slow traces and their logs in context.