<?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>Observability on Loop &amp; Retry</title>
    <link>https://loopandretry.github.io/tags/observability/</link>
    <description>Recent content in Observability on Loop &amp; Retry</description>
    <image>
      <title>Loop &amp; Retry</title>
      <url>https://loopandretry.github.io/images/og-default.png</url>
      <link>https://loopandretry.github.io/images/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Jul 2026 13:00:00 -0400</lastBuildDate>
    <atom:link href="https://loopandretry.github.io/tags/observability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Debugging a failed agent run costs more than the run itself</title>
      <link>https://loopandretry.github.io/posts/debugging-a-failed-run-costs-more/</link>
      <pubDate>Tue, 14 Jul 2026 13:00:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/debugging-a-failed-run-costs-more/</guid>
      <description>The cheap part of a failed agent run is running it again. The expensive part is that you can&amp;rsquo;t — the failure was non-deterministic, so the run that broke is gone, and you pay to summon it back. A cost model shows why reproduction, not repair, dominates your debugging bill, and why always-on tracing is almost always cheaper than the alternative it replaces.</description>
    </item>
    <item>
      <title>Your agent&#39;s failures are silent: measuring failure modes in production</title>
      <link>https://loopandretry.github.io/posts/measuring-agent-failure-in-production/</link>
      <pubDate>Mon, 13 Jul 2026 18:10:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/measuring-agent-failure-in-production/</guid>
      <description>Most agent failures don&amp;rsquo;t throw. The run returns a result, exit code zero, and the result is wrong — or it burns an hour and quietly gives up. If your monitoring only counts exceptions, you&amp;rsquo;re blind to the failures that actually cost you. A taxonomy of agent failure modes and the specific instrumentation that catches each one before your users or your bill do.</description>
    </item>
  </channel>
</rss>
