The Observant Developer — Continuous Feedback with OpenTelemetry
•
0 likes•395 views
This document discusses how continuous feedback platforms can help developers like Bill get faster feedback on code changes by collecting and analyzing telemetry data from production. It describes how Bill currently doesn't know if his code changes worked well, how they impacted the system, or if they were used. Continuous feedback platforms aim to close this gap by measuring changes in traces and spans over time to understand bottlenecks and how code is being used in production. They process telemetry data to provide insights with less expertise needed, focusing on code performance instead of only service metrics to create a more proactive development process.
Recommended
Recommended
More Related Content
Similar to The Observant Developer — Continuous Feedback with OpenTelemetry
Similar to The Observant Developer — Continuous Feedback with OpenTelemetry (20)
More from ScyllaDB
More from ScyllaDB (20)
Recently uploaded
Recently uploaded (20)
The Observant Developer — Continuous Feedback with OpenTelemetry
- 1. Brought to you by The Observant Developer Continuous Feedback with OpenTelemetry Roni Dover CTO at digma.ai
- 2. Roni Dover CTO at digma.ai ■ Board game geek ■ Multiclass PM/Developer/SM/Builder ■ Obsessed with evidenced-based dev ■ Recently started the digma.ai OSS digma.ai
- 3. Where I Spent Most of My Time
- 4. The Story of Bill
- 9. What will Bill do After Deploying the Feature?
- 10. The Story of Bill ■ Did my code change work well? ■ How did it alter system behavior? ■ Was it at all used?
- 11. Instead…
- 12. The Gap in the Feedback Loop
- 13. How I Want to Feel when Pushing to prod
- 14. How I Feel
- 15. What the PM Thinks
- 16. TFOTF at Shorter Intervals
- 17. Find the Missing Piece
- 18. TFOTF at Shorter Intervals
- 19. If only we had access to objective data about our code
- 21. Why is OTEL Important
- 22. The Story of Bill ■ Did my code change work well? ■ How did it alter system behavior? ■ Was it at all used?
- 23. Measuring Changes in Traces
- 24. Following Span Changes Over Time
- 26. The Story of Bill ■ Who is using this code? ■ Is this a critical area? ■ What should I optimize for?
- 28. We have Tons of Data… Why aren’t we using it?
- 29. Expertise Context Switching Dashboard Fatigue
- 33. My Personal Journey with CF
- 34. Mission Statement of CF Platforms ■ Process the data to glean insights and reduce expertise requirement ■ Focus on the code instead of only service metrics ■ Create a proactive process
- 35. Learn More About CF https://continuousfeedback.org/slack
- 36. Brought to you by Roni Dover rdover@digma.ai @doppleware