<p>I think the short answer is: You shouldn't define <strong>SLOs</strong>, if you don't have historical data.</p>

<p>With that being said, <strong>SLIs</strong> can be defined without historical data and correlated with KPIs and support metrics.</p>

<p>Here is a concrete example:</p>

<ul>
<li>Hipster store is about to launch.</li>
<li>Product management, dev and SRE wants to define SLOs.</li>
<li>They should start by defining SLIs, e.g site availability, sign-up success rate, checkout success rate.</li>
<li>PM/execs should agree to some kind of 'soft' launch and gradual rollout (if at all possible), e.g internal to employees -> partners -> single state/coast/country.</li>
<li>As the 'soft' and gradual rollout progresses, they can correlate swings in the SLIs with changes to KPIs (e.g revenue) and support metrics.</li>
</ul>

<p>At this point, the hipster store leadership would have some information about how much customer unhappiness/pain (e.g support metrics) and KPIs (e.g revenue) are correlated with SLIs. The SLOs are the bars. One or multiple can be set and alerts defined around them. Rinse and repeat.</p>

<p>A follow-up question is: How to alert and what to alert on before SLOs are set? I'd take the following article in consideration - <a href="https://www.oreilly.com/ideas/reduce-toil-through-better-alerting" rel="nofollow noreferrer">https://www.oreilly.com/ideas/reduce-toil-through-better-alerting</a>.</p>

CC BY-SA 4.0
2020-01-29T22:21:32.523Z
2020-01-29T22:21:32.523Z
Gustavo Franco
<p>Without much data you are really guessing, the general thought I have heard before is to start at 80% SLO then work your way up as you have data to back up your goal. There really is not set way of figuring out a SLO without some data. Even taking and using a week's data would be good enough to give you a reasonable idea.</p>

CC BY-SA 4.0
2019-10-23T17:58:09.247Z
2019-10-23T17:58:09.247Z
joshk132
<p>Assuming I can <a href="https://devops.stackexchange.com/questions/9542/how-to-start-defining-service-level-indicators-in-a-sre-organisation">define Service Level Indicators</a> for a user journey are there any structured methods for setting a Service Level Objective within that SLA without any historical data to indicate what is realistic or feasible? </p>

<p>For <strong>Availability</strong> we can often turn to various mathematical approaches that enable us to understand the maximum theoretical availability of the system, although even this is tied back to historical data in the form of Mean Time between Failure (MTBF) and Mean Time to Recover (MTTR).</p>

<monitoring><sre><operations>
How to define Service Level Objectives without historical data?
Richard Slater
# How to define Service Level Objectives without historical data?

(Asked by: username_0 on 2019-10-23)

Assuming I can [define Service Level Indicators](https://devops.stackexchange.com/questions/9542/how-to-start-defining-service-level-indicators-in-a-sre-organisation) for a user journey are there any structured methods for setting a Service Level Objective within that SLA without any historical data to indicate what is realistic or feasible?

For **Availability** we can often turn to various mathematical approaches that enable us to understand the maximum theoretical availability of the system, although even this is tied back to historical data in the form of Mean Time between Failure (MTBF) and Mean Time to Recover (MTTR).

**Tags:** monitoring, sre, operations


---

## 2 answers

### Answer by username_2 on 2019-10-23. Score: 1

Without much data you are really guessing, the general thought I have heard before is to start at 80% SLO then work your way up as you have data to back up your goal. There really is not set way of figuring out a SLO without some data. Even taking and using a week's data would be good enough to give you a reasonable idea.


---

### Answer by username_1 on 2020-01-29. Score: 0

I think the short answer is: You shouldn't define **SLOs**, if you don't have historical data.

With that being said, **SLIs** can be defined without historical data and correlated with KPIs and support metrics.

Here is a concrete example:

* Hipster store is about to launch.
* Product management, dev and SRE wants to define SLOs.
* They should start by defining SLIs, e.g site availability, sign-up success rate, checkout success rate.
* PM/execs should agree to some kind of 'soft' launch and gradual rollout (if at all possible), e.g internal to employees -> partners -> single state/coast/country.
* As the 'soft' and gradual rollout progresses, they can correlate swings in the SLIs with changes to KPIs (e.g revenue) and support metrics.

At this point, the hipster store leadership would have some information about how much customer unhappiness/pain (e.g support metrics) and KPIs (e.g revenue) are correlated with SLIs. The SLOs are the bars. One or multiple can be set and alerts defined around them. Rinse and repeat.

A follow-up question is: How to alert and what to alert on before SLOs are set? I'd take the following article in consideration - <https://www.oreilly.com/ideas/reduce-toil-through-better-alerting>.


---

