<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prometheus on SQP Dev</title>
    <link>/tags/prometheus/</link>
    <description>Recent content in Prometheus on SQP Dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/prometheus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a Homelab Monitoring Stack from Scratch</title>
      <link>/posts/2026-05-19-homelab-monitoring/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-19-homelab-monitoring/</guid>
      <description>&lt;p&gt;If you run a home server, you probably have a rough idea of whether things are working — you can SSH in, run &lt;code&gt;top&lt;/code&gt;, check disk space, maybe peek at some logs. But that&amp;rsquo;s reactive. You only look when something feels wrong. Proper monitoring means you know before something breaks, or at the very least, you know the moment it does.&lt;/p&gt;&#xA;&lt;p&gt;This is the story of how I set up a full observability stack on my home server, &lt;strong&gt;bitfrost&lt;/strong&gt; — an Ubuntu 24.04 machine running several Docker-based apps.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
