Distributed Request Tracing in .NET
summary
Overview of using Jaeger for distributed request tracing in .NET: what Jaeger (an Uber-built, Zipkin-inspired tracing system) collects, how it helps trace request paths and measure per-component time/latency, and what infrastructure is needed to add traces. Also introduces the OpenCensus library and the OpenTracing initiative as related tools for instrumenting .NET microservices for monitoring and performance analysis.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:42Distributed systems complexity
- 8:16Observability vs monitoring
- 10:27What is distributed tracing
- 13:35History of tracing systems
- 16:37Demo setup and Jaeger
- 24:03Tracing in .NET apps
- 27:56Cross-platform tracing demo
- 30:54Advanced tracing features
- 33:08How tracing works
- 37:19OpenTelemetry and standards
- 44:48OpenTelemetry overview
- 51:35Q&A
related talks
51mDistributed Tracing for microservices with Jaeger
41mDistributed Tracing in .NET
51mNavigating Distributed Traces
34mWould You Like Some Tracing With Your Monitoring?
28mJaeger Intro and Deep Dive
37mDeep Dive: Jaeger – Steve Flanders
40mCracking Microservices Performance Issues with Distributed Tracing
37mOpenTelemetry & Distributed Tracing: A Jaeger v2 Deep Dive