https://matijazezelj.github.io/packets-and-regrets/tags/observability/Recent content in Observability on Packets & RegretsHugoen-USSun, 19 Jul 2026 20:20:00 +0200https://matijazezelj.github.io/packets-and-regrets/posts/what-runs-in-the-home-lab/Sun, 19 Jul 2026 20:20:00 +0200https://matijazezelj.github.io/packets-and-regrets/posts/what-runs-in-the-home-lab/<p>At the publication snapshot, the two Docker hosts were running <strong>76 containers</strong>: 61 on the general application host and 15 on the specialist host.</p> <p>That is not 76 independent products. Sidecars, exporters, databases, browser workers, VPN helpers, and document processors inflate the container count. This inventory groups them by the job they perform instead of pretending every YAML service deserves its own logo wall.</p> <p>It also omits exact addresses, internal names, camera topology, credentials, firewall details, and management paths. A service catalogue should explain the system, not pre-write somebody else&rsquo;s reconnaissance report.</p>https://matijazezelj.github.io/packets-and-regrets/posts/prometheus-on-nfs-healthy-until-it-wasnt/Sun, 19 Jul 2026 19:30:00 +0200https://matijazezelj.github.io/packets-and-regrets/posts/prometheus-on-nfs-healthy-until-it-wasnt/<p>The monitoring page was green. The container was healthy. Queries worked.</p> <p>The storage design was still wrong.</p> <p>I had put the Prometheus time-series database on an NFS share. It was roomy, already mounted, and moved roughly 30 GiB away from a Docker VM whose local disk was tight. This seemed like a reasonable home-lab compromise right up to the moment the NAS stopped answering.</p> <p>Then Prometheus became the incident it was supposed to help explain.</p>