<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TSDB on Landry Zetam - Tech Blog</title><link>https://blog.landryzetam.net/tags/tsdb/</link><description>Recent content in TSDB on Landry Zetam - Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 18 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.landryzetam.net/tags/tsdb/index.xml" rel="self" type="application/rss+xml"/><item><title>Prometheus WAL Replay: When Your Metrics Database Can't Start Fast Enough</title><link>https://blog.landryzetam.net/posts/prometheus-wal-replay/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/prometheus-wal-replay/</guid><description>&lt;p>There&amp;rsquo;s a special kind of frustration that comes from watching a pod restart 90 times over 37 hours, each time getting &lt;em>just&lt;/em> a little further before Kubernetes kills it again. Today I debugged a Prometheus instance stuck in an infinite crash loop, and the root cause was surprisingly subtle: the database was simply too large to start within the default health check window.&lt;/p>
&lt;p>This is the story of startup probes, Write-Ahead Logs, and why your monitoring system might be the hardest thing to monitor.&lt;/p></description></item></channel></rss>