<?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>Loki on Alexander's Blog</title><link>https://alexanderbakin.com/tags/loki/</link><description>Recent content in Loki on Alexander's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 18:13:44 +0400</lastBuildDate><atom:link href="https://alexanderbakin.com/tags/loki/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting to 99.9%: Kubernetes and Real Observability for 20+ Microservices</title><link>https://alexanderbakin.com/k8s-observability/</link><pubDate>Mon, 15 Sep 2025 00:00:00 +0000</pubDate><guid>https://alexanderbakin.com/k8s-observability/</guid><description>&lt;p&gt;99.9% availability sounds like a slogan until you do the arithmetic: it&amp;rsquo;s a budget of roughly eight and a half hours of downtime for an entire year, across every service on the platform. Once you frame it that way, it stops being an aspiration and becomes an engineering constraint you either design for or blow through by month three. Getting there for a platform of 20+ microservices took deliberate work in two places that don&amp;rsquo;t get enough credit next to &amp;ldquo;just add more replicas&amp;rdquo;: the rollout path, and observability that&amp;rsquo;s actually fast enough to matter.&lt;/p&gt;</description></item></channel></rss>