<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ClickHouse on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/clickhouse/</link><description>Recent content in ClickHouse on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/clickhouse/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><item><title>RUM Time-Series Storage: Sentry, Datadog RUM and Grafana Faro</title><link>https://blog.mickeyzzc.tech/en/posts/telemetry/obs-tech-05-rum-storage/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/telemetry/obs-tech-05-rum-storage/</guid><description>&lt;p&gt;Real User Monitoring (RUM) differs fundamentally from backend monitoring in its data model: RUM collects &lt;strong&gt;event streams with massive high-cardinality attributes&lt;/strong&gt; — every user visit generates session_id, user_id, page_url, and hundreds of dimensions. Traditional TSDB label-set models degrade severely under this pattern.&lt;/p&gt;
&lt;p&gt;This article analyzes the time-series storage design of three mainstream RUM solutions: Sentry (open-source all-in-one), Datadog RUM (SaaS benchmark), and Grafana Faro (Grafana LGTM ecosystem extension). The common trend across all three is &lt;strong&gt;leveraging columnar OLAP instead of TSDB&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>eBPF Collection Storage and Observability Unified Architecture Trends</title><link>https://blog.mickeyzzc.tech/en/posts/telemetry/obs-tech-07-ebpf-unified-trends/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/telemetry/obs-tech-07-ebpf-unified-trends/</guid><description>&lt;p&gt;Observability architecture has undergone a profound shift from &amp;ldquo;fragmented&amp;rdquo; to &amp;ldquo;unified&amp;rdquo; over the past five years. Signals (metrics, logs, traces, profiling) have moved from independent specialized backends toward shared storage and a unified data model, while eBPF, as a next-generation collection mechanism, provides unprecedented data depth and breadth for this transformation. This article focuses on four dimensions: eBPF collection storage design, unified storage architecture (LGTM fragmented vs ClickHouse unified), the OpenTelemetry unified data model, and the evolution of object storage with compute-storage separation.&lt;/p&gt;</description></item></channel></rss>