<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Slo on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/slo/</link>
    <description>Recent content in Slo on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/slo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted SLO &amp; Error Budget Management: Sloth vs Pyrra vs OpenSLO</title>
      <link>https://www.pistack.xyz/posts/2026-05-13-self-hosted-slo-error-budget-management-sloth-pyrra-openslo-guide/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-13-self-hosted-slo-error-budget-management-sloth-pyrra-openslo-guide/</guid>
      <description>&lt;p&gt;Service Level Objectives (SLOs) and error budgets are the foundation of modern reliability engineering. An SLO defines the target level of service reliability that users expect, while an error budget quantifies how much unreliability is acceptable before action must be taken. Without proper tooling, tracking SLOs across dozens of microservices becomes a manual, error-prone process.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
