<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenTelemetry on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/opentelemetry/</link><description>Recent content in OpenTelemetry 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/opentelemetry/rss.xml" rel="self" type="application/rss+xml"/><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>