OTel community has been working on standardizing semantic conventions to correlate telemetry data from various systems. The Messaging SemConv aims to solve it for commonly used queues like Kafka, RabbitMQ, and others systems. OTel instrumentations are adopting these conventions, but the end users still face challenges with async messaging observability at scale. They struggle with questions like "how to trace message flow?", "how to correlate metrics with traces?", "how to do capacity planning and cost optimizations based on telemetry data?". The end-to-end visibility often remains a black box!
In this session, through a demo, we'll delve deeper into async architecture to address these questions, demonstrate context propagation within queues, and show how to correlate traces and client or broker-side metrics. Participants will gain hands-on experience with messaging instrumentation, learning how to achieve observability in both simple and complex asynchronous messaging scenarios.