Practical OpenTelemetry for .NET
summary
Concrete .NET how-to: set up tracing, metrics and soon logs with the OpenTelemetry SDK, configure ResourceBuilder so service.name is correct, and add an OTLP exporter to localhost:4318; use System.Diagnostics Meter for metrics and ActivitySource/Activity.Current for manual spans. Add built-in instrumentation with AddAspNetCoreInstrumentation, AddSqlClient and AddHttpClient (EntityFramework libraries are pre-release; Redis needs Configure). Warns baggage leaks PII (real Honeycomb incident), processors run on span end so affect latency, and recommends the collector for filtering, enrichment and tail‑sampling.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 6:07OpenTelemetry in .NET setup
- 11:25Metrics and instrumentation
- 18:58Manual tracing and spans
- 27:09Span attributes best practices
- 32:04Span events and error handling
- 34:10Span links and cross-process
- 38:02Processors and middleware
- 41:35Understanding and using baggage safely
- 47:37Custom propagations
- 52:15Sampling strategies
- 55:26OpenTelemetry Collector benefits
- 58:15Closing and resources
related talks
01h 01mPractical OpenTelemetry for .NET
01h 01mPractical OpenTelemetry in .NET 8
59mOpenTelemetry will save your day and night
56mGetting started with OpenTelemetry in .NET
01h 04mOpenTelemetry in a Brownfield World
01h 03mOpenTelemetry in a Brownfield World
51mOpenTelemetry tracing for .NET developers
21mUsing OpenTelemetry to Build More Human-Friendly Systems