<?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 Simple Enough Blog</title><link>https://blog.dev.simpleenough.net/tags/sre/</link><description>Recent content in SRE on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Jul 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.dev.simpleenough.net/tags/sre/index.xml" rel="self" type="application/rss+xml"/><item><title>MTTR: The Metric That Saves Your Nights</title><link>https://blog.dev.simpleenough.net/blog/mttr/</link><pubDate>Tue, 21 Jul 2026 10:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/mttr/</guid><description>&lt;p>It&amp;rsquo;s three in the morning, an alert fires, and the only question that matters isn&amp;rsquo;t &amp;ldquo;why did it break?&amp;rdquo; but &amp;ldquo;how long until it&amp;rsquo;s fixed?&amp;rdquo;. Trying to prevent every outage is an illusion: complex systems always end up failing. The real measure of a team&amp;rsquo;s maturity isn&amp;rsquo;t its ability to never fail, but its ability to &lt;strong>recover fast&lt;/strong>. That&amp;rsquo;s what MTTR measures — provided you know how to read it.&lt;/p></description></item><item><title>The Setups That Make Knowledge Circulate: Rotation, Game Days and Guilds</title><link>https://blog.dev.simpleenough.net/blog/dispositifstransmission/</link><pubDate>Mon, 20 Jul 2026 16:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/dispositifstransmission/</guid><description>&lt;p>In the guide to collaboration modes, we saw how to pass knowledge on in real time (the tacit) and in writing (the explicit). But a team can master all these practices and still watch its knowledge concentrate in a few people. The reason is structural: without a setup that forces it, knowledge follows the natural slope of specialization. This article deals with the organizational layer — not &lt;em>how&lt;/em> we work together, but &lt;em>how we arrange things&lt;/em> so that knowledge circulates by default.&lt;/p></description></item><item><title>Everyday Chaos Engineering: Learning to Love the Wave</title><link>https://blog.dev.simpleenough.net/blog/wave/</link><pubDate>Tue, 24 Mar 2026 10:00:00 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/wave/</guid><description>&lt;p>We all dream of a stable, predictable, “calm” system.
And yet, the reality of a modern platform is a living sea: deployments, external dependencies, cloud quotas, flaky networks, traffic spikes, human error—and sometimes… just “something” that should never have happened.&lt;/p>
&lt;p>Chaos engineering is often presented as a spectacular discipline—“we cut an AWS zone,” “we kill a cluster,” “we take Kafka down.”
In real life (and especially in small teams), that’s neither necessary nor desirable at the beginning.&lt;/p></description></item><item><title>Consumer-Reported Dependency Health</title><link>https://blog.dev.simpleenough.net/blog/dependencyhealth/</link><pubDate>Mon, 08 Dec 2025 11:18:06 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/dependencyhealth/</guid><description>&lt;h2 id="i-rethinking-how-we-evaluate-the-health-of-distributed-systems" class="heading">I. Rethinking How We Evaluate the Health of Distributed Systems&lt;a href="#i-rethinking-how-we-evaluate-the-health-of-distributed-systems" aria-labelledby="i-rethinking-how-we-evaluate-the-health-of-distributed-systems">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In modern distributed architectures, a system’s health depends as much — if not more — on the state of its &lt;strong>dependencies&lt;/strong> as on its own internal state. Yet most monitoring strategies still rely on synthetic or dedicated healthchecks: &lt;code>/health&lt;/code> endpoints, liveness/readiness probes, external scripts, and similar mechanisms.&lt;/p></description></item></channel></rss>