<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Exporter on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/exporter/</link>
    <description>Recent content in Exporter on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/exporter/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted eBPF Prometheus Exporters: Cloudflare vs dswarbrick vs DigitalOcean</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-self-hosted-ebpf-prometheus-exporters-cloudflare-dswarbrick-digitalocean-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-self-hosted-ebpf-prometheus-exporters-cloudflare-dswarbrick-digitalocean-guide/</guid>
      <description>&lt;p&gt;eBPF (extended Berkeley Packet Filter) has revolutionized Linux observability by allowing safe, in-kernel instrumentation of system calls, network events, and process behavior. When combined with Prometheus, eBPF exporters provide deep performance metrics without the overhead of user-space sampling. This guide compares three prominent eBPF-based Prometheus exporters: &lt;strong&gt;Cloudflare&amp;rsquo;s ebpf_exporter&lt;/strong&gt;, &lt;strong&gt;dswarbrick&amp;rsquo;s eBPF block I/O exporter&lt;/strong&gt;, and &lt;strong&gt;DigitalOcean&amp;rsquo;s Go eBPF exporter&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
