<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>EBPF on SRE &amp; AI Field Notes</title><link>https://sre-ai-blog.pages.dev/en/tags/ebpf/</link><description>Recent content in EBPF on SRE &amp; AI Field Notes</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 01:29:48 +0800</lastBuildDate><atom:link href="https://sre-ai-blog.pages.dev/en/tags/ebpf/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Millisecond-Level Observability with Prometheus + eBPF</title><link>https://sre-ai-blog.pages.dev/en/posts/ebpf-observability/</link><pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate><guid>https://sre-ai-blog.pages.dev/en/posts/ebpf-observability/</guid><description>&lt;h2 id="1-why-ebpf-observability"&gt;1. Why eBPF Observability&lt;/h2&gt;
&lt;p&gt;Traditional observability solutions rely on application instrumentation and sidecar proxies, introducing significant performance overhead and blind spots. eBPF allows safe execution of sandboxed programs within the kernel, capturing system calls, network packets, and file operations without modifying application code or introducing additional latency.&lt;/p&gt;
&lt;h2 id="2-three-layer-monitoring-with-ebpf"&gt;2. Three-Layer Monitoring with eBPF&lt;/h2&gt;
&lt;p&gt;We split observability into network, storage, and application layers. The network layer tracks TCP connection latency and retransmission rates via eBPF; the storage layer monitors file I/O and page cache hit rates; the application layer uses eBPF uprobes to capture key function call chains.&lt;/p&gt;
&lt;h2 id="3-prometheus-federation-architecture"&gt;3. Prometheus Federation Architecture&lt;/h2&gt;
&lt;p&gt;For multi-cluster scenarios, we adopted the Prometheus federation model: each cluster runs an independent Prometheus Server collecting eBPF-exported metrics, with a central Prometheus aggregating them for a global cross-cluster view.&lt;/p&gt;</description></item></channel></rss>