New Relic offers distributed tracing for monitoring and analyzing modern distributed systems.
To get started right away:
- Learn: Check out the different types of New Relic distributed tracing.
- Enable: See how to set up distributed tracing.
- Use: View your traces in the UI after you enable distributed tracing.
Why distributed tracing matters
When you can see software requests end-to-end, troubleshooting is easier and faster. Distributed tracing does this by showing you the path a request follows as it travels through a distributed system.
As requests travel between services, each segment is recorded as a span, which represents time spent in services or resources of those services. All the spans of a request are combined into a single distributed trace to give you a picture of an entire request.
Once your traces are captured in New Relic, you can use our powerful tools to analyze them:
- Filter results: You can filter charts using many data points, so you can analyze trace data in different ways.
- Detect anomalous spans: Spans that are slow in comparison to typical behavior are marked as anomalous, with charts comparing them to typical instances.
- Customize queries and dashboards: You can create custom queries of your trace data and create custom data dashboards.
- See data across accounts: In New Relic One, see a global view of traces from across all your accounts and applications.
- Query traces programmatically: Query distributed trace data by using GraphQL in our NerdGraph API explorer.