<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tracing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/tracing/</link>
    <description>Recent content in Tracing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/tracing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>bpftrace vs BCC vs Sysdig: Best eBPF Tracing Tools 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-26-bpftrace-vs-bcc-vs-sysdig-self-hosted-ebpf-tracing-guide-2026/</link>
      <pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-26-bpftrace-vs-bcc-vs-sysdig-self-hosted-ebpf-tracing-guide-2026/</guid>
      <description>&lt;h2 id=&#34;why-self-host-ebpf-tracing-tools&#34;&gt;Why Self-Host eBPF Tracing Tools&lt;/h2&gt;&#xA;&lt;p&gt;Linux system troubleshooting has historically required either expensive commercial APM suites or cumbersome kernel modules that destabilize production systems. The introduction of &lt;a href=&#34;https://ebpf.io/&#34;&gt;eBPF (extended Berkeley Packet Filter)&lt;/a&gt; changed this entirely — providing a safe, sandboxed way to observe and modify kernel behavior without loading kernel modules or rebooting.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
