<p>it sounds as though the concept of "burst limits" may apply here. If high reliability is needed during foreseen special events of a generally similar duration, it probably is also needed during emerging events too. I suggest broad timescale SLOs (e.g. 99.9% successful responses per month) plus sliding SLOs based on demand, or fixed-limit SLOs instead of rates. An example might be, 99.95% successful responses at 1000qps, 99.99% success at 5000qps. Or, 99.9% successful responses, and no more than 5 failures per second regardless of load.</p>

CC BY-SA 4.0
2019-03-27T13:36:09.520Z
2019-03-27T13:36:09.520Z
Jonathan Solórzano-Hamilton
<p>Special events such as BFCM (Black Friday / Cyber Monday).</p>

CC BY-SA 4.0
2019-03-24T06:52:03.683Z
Hi Gustavo, welcome to DevOps SE. It's going to be a little hard to answer your question as it is; is there any further information you can provide to help us understand what you're trying to achieve? See https://devops.stackexchange.com/help/how-to-ask for some tips; in particular, knowing what you've come up with so far will help us more specifically hone in on what you're after.
Tim Malone
CC BY-SA 4.0
2019-03-25T04:05:57.833Z
Hi Tim, thanks for the reference. I'm trying to establish how SREs in other companies (other than mine/Google) approach things such as https://cloud.google.com/blog/products/management-tools/tune-up-your-sli-metrics-cre-life-lessons.
Gustavo Franco
<sre>
How do you write an SLO for a service when higher reliability is needed only during special events?
Gustavo Franco
# How do you write an SLO for a service when higher reliability is needed only during special events?

(Asked by: username_0 on 2019-03-22)

Special events such as BFCM (Black Friday / Cyber Monday).

**Tags:** sre

> **Comments:**
> **username_1**: Hi Gustavo, welcome to DevOps SE. It's going to be a little hard to answer your question as it is; is there any further information you can provide to help us understand what you're trying to achieve? See https://devops.stackexchange.com/help/how-to-ask for some tips; in particular, knowing what you've come up with so far will help us more specifically hone in on what you're after.  
> **username_0**: Hi Tim, thanks for the reference. I'm trying to establish how SREs in other companies (other than mine/Google) approach things such as https://cloud.google.com/blog/products/management-tools/tune-up-your-sli-metrics-cre-life-lessons.  

---

## 1 answers

### Answer by username_2 on 2019-03-27. Score: 1

it sounds as though the concept of "burst limits" may apply here. If high reliability is needed during foreseen special events of a generally similar duration, it probably is also needed during emerging events too. I suggest broad timescale SLOs (e.g. 99.9% successful responses per month) plus sliding SLOs based on demand, or fixed-limit SLOs instead of rates. An example might be, 99.95% successful responses at 1000qps, 99.99% success at 5000qps. Or, 99.9% successful responses, and no more than 5 failures per second regardless of load.


---

