An availability objective is set
The service has a stated availability target, so "is it reliable enough?" has an answer.
HighChecked automatically
- Applies to:
- Every service
- Rule id:
- observability.availability-slo
Why it matters
Without a target every outage is equally bad and every reliability project equally urgent. A target tells the team when to stop shipping features and fix stability, and tells callers what they can build on. It also sets the timeouts, replica counts and dependency choices in the rest of the design.
How to apply it
- State the objective as a percentage over a window, measured where the user feels it: "99.9% of requests succeed over 30 days".
- Choose it from what users need, not from what looks good. Each extra nine costs roughly ten times more.
- A service can't promise more than the hard dependencies it calls. Check their objectives first.
- Derive the error budget from it and agree what happens when it runs out.
Example
slo.availability: 99.9% over 30 days, which allows about 43 minutes of failed requests per month.
References
Checklists with this rule
Related agent skill: observability