CNCF-hosted Co-located Events North America 2024

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.

Our team at monday.com has experienced explosive growth over the past four years. We prioritized enabling tracing and observability across our distributed app. However, we did not have robust end-to-end tests. Building reliable end-to-end tests for distributed apps is hard! We decided to use OpenTelemetry tracing for end-to-end testing as well and adhering to our “Observability Everywhere” mantra! In this talk we’ll showcase how we implemented trace-driven testing with Tracetest and OpenTelemetry. This improved our feedback cycle by 50%, uncovered issues that traditional tests missed and decreased test creation time by 90%! Attendees will also learn how to apply this new approach to various use-cases, such as API tests, browser end-to-end testing and even testing in production. Trace-driven testing works by leveraging the work already invested in instrumenting our systems via distributed tracing. Sounds fun? Join me to learn how we did it at monday.com!

Like many enterprises, we at Dynatrace deal with multiple delivery streams and various tooling to be used to develop, build, test and deliver our product to our customers. To better scale and have a resilient delivery practice, we regularly need to streamline the processes. From a requirement till the running solution, it typically involves many steps, often various people and different systems. Distributed knowledge makes it hard to transparently identify issues and slows things down. Observability in SDLC (Software Delivery Lifecycle) is our key enabler that gives us insights into resources, tools, techniques, staging, quality, rollout, etc. In this session learn how we automatically trace every delivery value flow, identify bottlenecks, wait times, lead times and other characteristics with the help of cloud native observability. Observability tells us where to start with optimization(s) and how to apply a continuous improvement cycle to our delivery chain.