<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Log Storage on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/log-storage/</link><description>Recent content in Log Storage on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/log-storage/rss.xml" rel="self" type="application/rss+xml"/><item><title>Log Storage Architecture: From Inverted Indexes to Weak Indexing</title><link>https://blog.mickeyzzc.tech/en/posts/telemetry/obs-tech-03-log-storage/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/telemetry/obs-tech-03-log-storage/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Logs generate the largest data volume and highest storage cost among the three pillars of observability. Unlike metrics with their fixed numeric structure, logs are variable-length text with semi-structured characteristics, posing unique storage design challenges: supporting full-text search while controlling storage costs.&lt;/p&gt;
&lt;p&gt;The core design dimension of log storage systems is &lt;strong&gt;indexing strategy&lt;/strong&gt; — deeper indexing means faster search, but also higher storage costs. From Elasticsearch&amp;rsquo;s full inverted index to Loki&amp;rsquo;s label-only indexing, each system makes different technical choices along this spectrum.&lt;/p&gt;</description></item></channel></rss>