<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sre on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sre/</link>
    <description>Recent content in Sre on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 23 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sre/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Sloth vs Pyrra vs SLO Generator: Best Self-Hosted SLO Management Tools 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-23-sloth-vs-pyrra-vs-slo-generator-self-hosted-slo-management-guide/</link>
      <pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-23-sloth-vs-pyrra-vs-slo-generator-self-hosted-slo-management-guide/</guid>
      <description>&lt;p&gt;Service Level Objectives (SLOs) are the cornerstone of modern Site Reliability Engineering. They define the reliability target your service promises to users, translate complex metrics into business-readable goals, and drive engineering decisions through error budget tracking. But implementing SLOs by hand — writing PromQL queries, calculating burn rates, configuring multi-window alerts — is error-prone and scales poorly across teams.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
