SLO Creation And You: Or, How We Learned To Stop...
summary
FreshBooks pilots SLOs on rabbitmq, replacing noisy queue-length alerts with measured time in queue and a new 99.95% monthly availability objective. The team writes instrumentation to track message latency, creates recovery objectives, and defines an observable target—deliver 99% of signup emails in under two minutes. The pilot exposes surprising noise in historic alerts, enables capacity forecasting from the new metrics, and shifts responsibility to service owners; the instrumentation and objectives prove effective in practice.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:20About Lisa
- 0:40About Freshbooks
- 3:11Act 1 SLO Creation
- 4:13Monthly Availability
- 4:39SLO Backstory
- 5:21Reaction
- 5:49Backlog
- 6:09Ontario Canada
- 6:20Bug
- 6:32Capacity Planning
- 6:58RabbitMQ Concerns
- 8:41Asking Questions
- 9:15What Do We Gain
- 10:32Socialize Our Objectives
- 11:26Reframe The Questions
- 12:50RabbitMQ
- 13:40What does misuse of our services look like
- 14:16Minimize customer wait time
- 16:11throughput
- 16:37Q Limits
- 18:12Q Lengths
- 19:00Assess
- 19:43Historic Pitfalls
- 20:57Our Journey
- 22:01Wrapping Up
- 23:13Learn More
related talks
31m9 Things You Should Do When Starting to Use SLOs
33mHow and why we lowered our SLO
31mServerless Observability: a case study of SLOs
06ma pint sized introduction to SLO
38mImplementing SRE practices: SLI/SLO deep dive
30mMetrics for good, not evil
35mAvoiding Goodhart's Law - Use SLO's as Tools Not Cudgels
28mLean Product Development Through SLOs