OpenTelemetry in a Brownfield World
summary
Brownfield .NET microservices move from console logs and Splunk to OpenTelemetry by adding a log4net → Microsoft.Extensions.Logging bridge, enabling built-in instrumentations (ASP.NET, HttpClient, EntityFramework, RabbitMQ, MongoDB), and exporting traces to an OpenTelemetry Zipkin exporter while viewing locally with the Aspire dashboard. The migration includes hand‑written spans via ActivitySource for migrations, produces structured logs and SQL/HTTP spans, and runs end to end locally (traces appear in Zipkin), reducing vendor lock‑in.
AI-written summary · about
chapters (10)
- 0:00OpenTelemetry intro in brownfield
- 6:21What is observability
- 15:30Legacy app telemetry challenges
- 21:50Adopt OpenTelemetry in brownfield
- 24:18Migration strategy to OpenTelemetry
- 33:55Migrate logging to OpenTelemetry
- 43:47Tracing in distributed systems
- 51:17Demo: OpenTelemetry in .NET
- 1:00:05Custom traces and metrics
- 1:02:56Summary and next steps
related talks
01h 03mOpenTelemetry in a Brownfield World
59mOpenTelemetry will save your day and night
01h 00mPractical OpenTelemetry for .NET
56mGetting started with OpenTelemetry in .NET
51mOpenTelemetry tracing for .NET developers
01h 01mPractical OpenTelemetry for .NET
01h 01mPractical OpenTelemetry in .NET 8
20mObservability and Open Telemetry