Observability
SLOs That Survive Reorgs and Vendor Changes
Draft error budgets that connect customer journeys to service graphs, including how to renegotiate SLOs after acquisitions.
3 days, virtual · Virtual intensive · starts
₩2,400,000 · informational reference only
Program narrative
Participants iterate on SLO drafts with dependency graphs, customer support excerpts, and finance-friendly translations of risk.
What is included
- Journey-to-service mapping exercises
- Translation worksheet for finance partners
- Burn rate alert templates
- Dependency risk scoring
- Vendor migration checklist for SLO continuity
- Quarterly review cadence proposal
- Leadership workshop facilitation guide
Outcomes
- Publish three journey-level SLOs with explicit exclusions
- Define burn-rate policies with paging thresholds
- Capture vendor-specific measurement gaps
Jonah Park
Lead microservices instructor with a background in high-volume fintech pipelines.
Participant questions
Read-only metrics access helps but synthetic data can substitute.
Recent participant notes
SLO Survival Lab connected our fragmented Grafana boards to actual customer complaints. Minor note: one exercise assumed Kubernetes metrics.