Observability
Signals & SLO Studio
Design service level objectives that match user journeys, not vanity graphs.
5 weeks · 26h · Cohort + async labs · BRL 1.890 (informational)
Program narrative
You translate ambiguous reliability goals into measurable signals, burn budgets, and review cadences that platform teams can defend in production reviews.
What ships inside
- Multi-window burn alerting playbooks
- User-journey mapping for SLIs
- Error budget policy templates
- Dashboard critique rubric
- Synthetic vs real traffic tradeoffs
- Stakeholder review agenda pack
- Exportable SLO registry schema
Outcomes we expect you to demo
- Publish a three-tier SLO set for one critical path
- Run a monthly error budget review with notes
- Instrument missing signals without duplicating metrics
Mentor on point
Helena Prado
Reliability lead focused on telemetry contracts and SLO governance.
FAQ — including what we skip
We stay vendor-neutral on agents but show wiring patterns for OpenTelemetry exporters you can map to your stack.
Experience notes
“The burn budget workshop finally made our SLO deck legible to product—not just graphs for ops.”
— Rafa · Platform engineer · 5/5 · survey
“Loved the SLI mapping worksheet; still wish the Prometheus section had one more lab hour.”
— Camila · Regional SaaS group · 4/5