<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sre on IT Comparison</title><link>https://comparison.metacog.co.kr/tags/sre/</link><description>Recent content in Sre on IT Comparison</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 02 Aug 2026 08:34:10 +0900</lastBuildDate><atom:link href="https://comparison.metacog.co.kr/tags/sre/index.xml" rel="self" type="application/rss+xml"/><item><title>Monitoring vs Observability: Knowing Something's Wrong vs Knowing Why</title><link>https://comparison.metacog.co.kr/posts/2026-08-02-monitoring-vs-observability-knowing-something-s-wrong-vs-kno/</link><pubDate>Sun, 02 Aug 2026 08:34:10 +0900</pubDate><guid>https://comparison.metacog.co.kr/posts/2026-08-02-monitoring-vs-observability-knowing-something-s-wrong-vs-kno/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Monitoring watches a predefined set of metrics, logs, and checks against known failure modes and alerts you when thresholds are breached. Observability is a property of a system built so that its internal state can be inferred from its external outputs, letting you investigate questions you didn&amp;rsquo;t think to ask in advance. The distinction matters because monitoring answers &amp;lsquo;is something wrong?&amp;rsquo; while observability answers &amp;lsquo;why is it wrong?&amp;rsquo; for failures you&amp;rsquo;ve never seen before.&lt;/p&gt;</description></item></channel></rss>