---
title: "Comment by Abhinav Sharma on \"SRE Fundamentals: Designing SLIs, SLOs and Error Budgets\" | Hashnode"
description: "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 t"
url: "https://hashnode.com/posts/sre-fundamentals-designing-slis-slos-and-error-budgets/6ada3bdf150eae9ef93df87e/comment/6ada5ddc106819373ed56108"
---

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

Comment [SRE Fundamentals: Designing SLIs, SLOs and Error Budgets](https://hashnode.com/posts/sre-fundamentals-designing-slis-slos-and-error-budgets/6ada3bdf150eae9ef93df87e)

[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.