Our Experience Tracking and Driving SLO Adoption at Goldman Sachs
summary
Goldman Sachs builds a configuration-driven dashboard called SLO Repository (internal name SLO Poetry) that exposes SLIs as short-window status-first tiles, links each tile to Grafana graphs and the underlying YAML, and supports onboarding phases draft → incubating → live. Teams instrument user-centric SLIs with synthetic probes, view 1-week and 28/31-day histories, and get postmortem and dependency discovery integration. The result: faster adoption because stakeholders see service health immediately, signal-quality audits surface bad metrics, and teams iterate SLOs instead of ignoring error-budget graphs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 3:41The Problem
- 5:39Reactive Alerts
- 6:37The Journey
- 9:26Other Problems
- 10:16SLO
- 14:04Long periods
- 15:33Dashboards
- 16:38What is SLOPoetry
- 18:26What is Status
- 20:49What is Downtime
- 22:36What is Supporting Service
- 27:04LongTerm Reporting
- 29:48Challenges
- 31:57Service Phase
- 35:33SLO Platform
- 38:44Lessons Learned
- 41:00Recap
related talks
18mSLICK: Driving SLO Culture
32m9 Things You Should Do When Starting to Use SLOs
40mScaling SLOs with Kubernetes and Cloud Native Observability
22mLook Ma, No Metrics: A Quest Towards Extracting SLOs
23mGrafana SLO Demo: Prioritize critical resources with SLO-driven IRM
37mReal World SLOs and SLIs: A Deep Dive
23mHow We Built a Complex SLO App Tightly Integrated with Grafana
57mSLI and SLO for the Business: Monitoring Quality Across 200+ Products