<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reliability on Mikolaj Karebski - Engineering Notes</title><link>https://blog.karebski.dev/tags/reliability/</link><description>Recent content in Reliability on Mikolaj Karebski - Engineering Notes</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.karebski.dev/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>SRE Starts When Metrics Influence Decisions</title><link>https://blog.karebski.dev/posts/sre-starts-when-metrics-influence-decisions/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.karebski.dev/posts/sre-starts-when-metrics-influence-decisions/</guid><description>I&amp;rsquo;m currently rereading Google&amp;rsquo;s Site Reliability Engineering book, and it made me think about how companies adopt SRE in practice.
Many companies naturally adopt parts of SRE as their systems grow. They add monitoring, alerting, dashboards, incident reviews, and postmortems because at some point operating without them becomes too painful.
But there is an important step that is easier to miss: connecting those signals back to business decisions.
Reliability metrics should not live only in engineering dashboards.</description></item></channel></rss>