Using OpenTelemetry to Improve Service Level Objectives
summary
Argues that OpenTelemetry supplies the actual instrumentation developers need to implement SLOs, turning hope-based deployments into data-driven releases. Demonstrates mapping OpenTelemetry libraries in Visual Studio Code to acceptance criteria, uses a GitHub demo app and shows Coralogix SLO Center reporting compliance, error budget and burn rate. Gives a concrete SLO example—99% of API responses ≤250ms—and describes enforcing instrumentation during pull-request reviews so features ship observable, testable reliability rather than just code.
AI-written summary · about
chapters (9)
- 0:00Introduction and Welcome
- 0:23Speaker Background and Experience
- 0:43Passion for Technology and Coding Journey
- 1:57Introduction to Open Telemetry
- 5:09Importance of Customer Trust
- 6:44Understanding Service Level Objectives (SLOs)
- 9:37Integrating SLOs into Development
- 17:13Demo: Implementing Open Telemetry
- 23:14Q&A Session
related talks
39mShifting Left on Production Excellence with Observability
50mOpen Telemetry: The Rise of Open Standards in Observability
17m“How’s the App Doing?” Bringing Mobile Into Your Reliability Picture
40mScaling SLOs with Kubernetes and Cloud Native Observability
32m9 Things You Should Do When Starting to Use SLOs
22mOpen Telemetry for API Monitoring
50mGuide to Observability with OpenTelemetry
47mService Level Objectives as Code: Bootstrapping SLOs with Terraform