Loading video player...
Observability got bigger than “three pillars” and a dashboard. Observability 2.0 is about correlation, not collection, so teams can ask meaningful questions and get useful answers. In this Thunder episode, Whitney Lee and guest Adriana Villela discuss how the OpenTelemetry model aligns signals into one story across the software development lifecycle. They walk through a practical flow: instrument code first, let QA use telemetry (or ask for more), add trace-based testing for integration checks, and help SREs anchor SLIs/SLOs to traces so incidents stop feeling like needle-in-a-haystack hunts. They also show why CI/CD should emit telemetry and where today’s tooling stands. Discover practical implementation steps for developers, QA teams, and SREs to improve system visibility and detect problems before users do. Whether you're new to observability or looking to modernize your approach, this episode provides clear explanations and actionable insights for better system monitoring. 0:02 - 0:35 Introductions of Whitney and Adriana. 0:35 - 3:49 Recap of observability 1.0 basics. 3:49 - 4:02 Development and evolution analogy used. 4:02 - 4:53 Introduction to observability 2.0 concepts. 4:53 - 13:25 Detailed open telemetry and tracing. 13:26 - 17:35 Observability in CI/CD pipelines. 17:37 - 17:49 Concluding thoughts and goodbyes. Prefer the full ⚡ Enlightning episode? Observability 2.0: Not Just Another Buzzword → https://www.youtube.com/watch?v=dcVD6sNtAiI Watch all ⚡ Enlightning episodes → https://www.youtube.com/playlist?list=PLBexUsYDijaz09nH8BVPmPio_16V115i4 Watch all 🌩 Thunder episodes → https://www.youtube.com/playlist?list=PLBexUsYDijawXI7x707H1YDdNT2vi98e _ ٩( ᐛ )و Subscribe to Whitney’s YouTube channel → https://www.youtube.com/@wiggitywhitney #Observability #OpenTelemetry #SRE #Tracing #CICD ▬▬▬▬▬▬ ⚡️ Related Links ⚡️ ▬▬▬▬▬▬ 🔗 OpenTelemetry → https://opentelemetry.io/ 🔗 Trace-based testing (Tracetest) → https://tracetest.io/ 🔗 CNCF Slack → https://slack.cncf.io/