---
title: "Discussion on \"SRE Fundamentals: Designing SLIs, SLOs and Error Budgets\" | Hashnode"
description: "Discussion on \"SRE Fundamentals: Designing SLIs, SLOs and Error Budgets\". Define a checkout attempt, measure usable responses, and decide when reliability work should take priority."
url: "https://hashnode.com/posts/sre-fundamentals-designing-slis-slos-and-error-budgets/6ada3bdf150eae9ef93df87e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [SRE Fundamentals: Designing SLIs, SLOs and Error Budgets](https://blog.turingts.com/sre-fundamentals-designing-slis-slos-and-error-budgets?utm_source=hashnode&utm_medium=feed)

Define a checkout attempt, measure usable responses, and decide when reliability work should take priority.

Oct 22 · 13 min read · blog.turingts.com  
Read the article

-   [#sre](https://hashnode.com/tag/sre)
-   [#site-reliability-engineering](https://hashnode.com/tag/site-reliability-engineering)
-   [#prometheus](https://hashnode.com/tag/prometheus)
-   [#observability](https://hashnode.com/tag/observability)

## Written by

[Ferhat Yildiz](https://hashnode.com/@turingts)

@turingts · Amstelveen, Netherlands

  
[View profile](https://hashnode.com/@turingts)

Owner at Turing Technology Services

I’m a hands-on technology architect, engineer and founder of Turing Technology Services, with nearly two decades of experience in software engineering, platform engineering, site reliability engineering and cloud infrastructure. My work combines architecture and implementation with technical leadership, coaching and helping organisations adopt new engineering practices. I’ve worked with organisations including Shell, ING, ABN AMRO, Rabobank, Schiphol Group and Ahold Delhaize, across complex and regulated enterprise environments. On this blog, I share practical guides and perspectives on software architecture, cloud platforms, reliability and AI, explaining the reasoning behind technical choices as well as how to implement them.

## Responses 1

Comments are turned off for this post.

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 22](https://hashnode.com/posts/sre-fundamentals-designing-slis-slos-and-error-budgets/6ada3bdf150eae9ef93df87e/comment/6ada5ddc106819373ed56108)

The error budget framing is what makes SLOs actionable: 99.9% over 30 days is about 43 minutes of allowed badness, and once that is spent the policy answer is to freeze features, not argue about dashboards. Multi-window burn-rate alerts catch both the sudden outage and the slow leak.