SLO Time Windows: Rolling vs Calendar
You'll learn: How to choose between rolling and calendar time windows when measuring whether your service meets its SLO targets.
The Core Problem
When you set an SLO (like "99.9% uptime"), you need to define over what time period you're measuring. Two common approaches exist: rolling windows and calendar windows. Each changes how you evaluate compliance and respond to incidents.
Calendar Windows
Calendar windows align to fixed periods: monthly (January 1-31), quarterly, or yearly. Think of it like a report card that resets every semester.
Pros:
- Simple budgeting: "We have 43 minutes of downtime left this month"
- Predictable reset points
- Easy to communicate to stakeholders
Cons:
- You can burn your entire error budget on day 1 and still be "in compliance" by month's end if nothing else breaks
- Gaming the system: teams might be more aggressive near month-end after incidents heal
Rolling Windows
Rolling windows look at the last N days continuously—like a sliding window that moves forward every moment. Measuring "99.9% over the last 30 days" means yesterday's incident still counts today.
Pros:
- More accurate real-time view of reliability
- Recent incidents always affect current compliance
- Prevents end-of-period gaming
Cons:
- Harder mental model for stakeholders
- More complex to calculate and explain
- A single bad day haunts you for the full window duration
Key Takeaway
Rolling windows provide continuous, up-to-date reliability signals but are harder to reason about; calendar windows are simpler and align with business cycles but can hide recent problems—choose based on whether you prioritize real-time accuracy or stakeholder simplicity.