While APM transaction tracing is helpful for analyzing calls in a single application, distributed tracing broadens your view by showing the path a request takes across multiple applications and services–from start to finish. With this wider view, you can quickly troubleshoot performance bottlenecks and errors.
In this practical session you’ll find out about how New Relic Distributed Tracing can extend your transaction tracing capabilities, and understand how Distributed Tracing works and can be configured for different environments. Using a sandbox account you’ll get hands-on experience of the different ways of working with the UI, combining it with APM and Logs data, and using it to solve a range of problems.
- Intro to Distributed Tracing: What it is, why it’s important
- Real world use cases
- Tracing in New Relic UI: Tracing walkthrough
- Lab: Explore Distributed Tracing
- How Distributed Tracing works
- Trace context and Spans
- Trace Sampling: Head (Standard) and Tail based Sampling (Infinite Tracing)
- How to configure: options for Standard and Infinite Tracing, New Relic Edge
- Find and Fix workshop
- Labs: Issues with a specific Service, time periods & errors, outliers
- Summary and Takeaways