Diana is a Developer Experience Engineer at VictoriaMetrics. She has worked as a Senior Site Reliability Engineer focused on Observability. She is an active member of the OpenTelemetry CNCF open source project, co-organizer of Cloud Native Days Romania, co-lead of neurodiversity working group (part of CNCF initiative merge-forward) and supports underrepresented groups in tech.
We keep telling developers they need to instrument their own code with OpenTelemetry (OTel). When they do, it feels like they’re doing it for the benefit of others, like SREs. Observability can benefit developers too, but it feels too complicated, and as a result Observability is treated as a second-class citizen.
This talk changes that by motivating developers to troubleshoot their own code with OTel. Developers will learn:
- Why do it?
- Basic overview of OTel instrumentation concepts
- Overview of desktop tooling for developers to visualize OTel data
- How to add meaningful traces, metrics, and logs to your code with minimal changes
- A practical, repeatable workflow for using OTel to troubleshoot code
- Common pitfalls (like accidental high cardinality) and how to avoid them
- A live demo putting it all together
Developers will walk away with the confidence to instrument and troubleshoot their own code with OTel.
Searching for speaker images...