The Observant Developer - OpenTelemetry from code to prod
summary
Claims that OpenTelemetry plus continuous feedback turns production telemetry into actionable dev signals, not just dashboards. Uses FastAPI, RabbitMQ (Pika), Postgres (SQLAlchemy), exports to Jaeger, and demonstrates a sample Gringotts Vault API. Finds out-of-the-box instrumentation across libraries, surfaces an N+1 query discovered from real traces, and wires an IDE plugin plus a continuous-feedback pipeline (digma) to highlight hotspots. Outcome: running app emits rich traces and the developer sees concrete, fixable issues in production context.
AI-written summary · about
chapters (10)
- 0:00Observability with OpenTelemetry
- 3:25Modern developer's role
- 8:46Missing feedback loop
- 13:25OpenTelemetry debugging
- 17:57Traces with Jaeger
- 21:10Observability in development
- 24:03Why ignore observability data
- 25:48Continuous feedback in IDE
- 29:01Getting started with feedback
- 31:50Cultural shift to observability
related talks
35mOpenTelemetry for Busy People
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
52mGraphQL Observability with Elastic and OpenTelemetry
02h 02mHow To Troubleshoot and Monitor Applications using OpenTelemetry
49mAdding OpenTelemetry to Production Apps Lessons Learned
37mObservability For You And Me With Opentelemetry
19mInstrumenting Go Apps With OpenTelemetry
41mModern Application Debugging: An Introduction To OpenTelemetry