OpenTelemetry and Continuous Feedback – Things you need to Know at Runtime
summary
Argues that embedding runtime feedback into the IDE reveals real issues fast: enabling OpenTelemetry via env vars feeds traces into tools like jger, and an IDE plugin called digma surfaces hotspots automatically (it detects a slowdown and an N+1 that causes 97 queries for one endpoint). The setup needs no code changes, runs on OSS, and shifts from manual trace hunting to continuous automated analysis so problems appear where code lives.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 3:51What do I know about my code
- 11:15Practical feedback examples
- 16:20OpenTelemetry observability basics
- 23:39Limitations of manual feedback
- 25:48Continuous feedback with IDE plugin
- 30:05Key challenges and resources
related talks
51mCoding with the lights ON - OpenTelemetry from code to prod
33mThe Observant Developer - OpenTelemetry from code to prod
55mCoding with the lights ON - OpenTelemetry from code to prod
41mModern Application Debugging: An Introduction To OpenTelemetry
40mContinuous Profiling, the missing piece in your observability puzzle!
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
36mFind and fix performance issues in your code usign Digma
35mOpenTelemetry for Busy People