Observability for Developers: What You Need to Know?
About this video
What You'll Learn
- Understand why developers own instrumentation and when observability teams should not own production code signals.
- Compare OpenTelemetry auto and manual instrumentation, including when zero-touch coverage adds too much noise or technical debt.
- Use sampling, feature flags, and collector routing to balance telemetry coverage with dollar cost, storage, and environmental impact.
Adriana Villela explains why developers, not observability teams, should instrument their own code. We cover OpenTelemetry's auto vs manual instrumentation, sampling and cost trade-offs, single-pane-of-glass backends, and the environmental impact of telemetry.
Meet the Cast
Weekly Cloud Native insights
Stay ahead in cloud native
Tutorials, deep dives, and curated events. No fluff.
More from Cloud Native Compass
View all 23 episodes
39:59
Navigating Kairos: Immutable Operating Systems with a Cloud Native Twist
51:20
Flatcar Linux: A Modern OS for the Always-On Infrastructure
43:56
Platform Engineering: Asking "Why"? with Evelyn Osman
41:58
AI-Augmented Programming
47:55
The Future of Sustainability in Open Source
39:31
Atlantis: The Terraform Automation Powerhouse
More about OpenTelemetry
More about Jaeger
Comments