<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Monitoring on Foogar</title>
    <link>https://www.foogar.com/tags/monitoring/</link>
    <description>Recent content in Monitoring on Foogar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 13 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.foogar.com/tags/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Dashboard That Cried Wolf</title>
      <link>https://www.foogar.com/posts/2026-10-13-the-dashboard-that-cried-wolf/</link>
      <pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.foogar.com/posts/2026-10-13-the-dashboard-that-cried-wolf/</guid>
      <description>&lt;p&gt;The alert arrived as a question, not a page: &lt;em&gt;why is memory pinned near the top?&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;I went to look. The summary panel for the machine that hosts this home&amp;rsquo;s brain&#xA;showed memory almost fully consumed - the kind of number that, on another day,&#xA;would have sent me straight into the logs at speed. But it didn&amp;rsquo;t behave like a&#xA;leak. It sat high and flat: never climbing, never easing. Alarming, and&#xA;suspiciously calm.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
