From Tool To ToolBox: How bpftrace is evolving to become more composa...
summary
bpftrace is moving from a single-tool language to a composable toolbox: the project reports ~10,000 lines of user scripts vs ~30,000 lines of bpftrace code and is adding hygienic macros for code reuse, imports of BPF C files so custom kernel helpers compile and link on the fly, compile-time features like a comp time builtin with branch pruning and type introspection, and a maintained standard library plus a web playground and Discord to accelerate real-world adoption.
AI-written summary · about
chapters (7)
- 0:00Introduction to bpftrace
- 3:49Limitations of bpftrace today
- 7:38Evolving bpftrace for composability
- 13:00Importing C code into bpftrace
- 16:58Building a bpftrace standard library
- 19:23Discussion on kernel versions and synthetic events
- 21:09Future of bpftrace libraries
related talks
35mbpftrace: Evolution from a command line tool to a complex observability framework
46mbpftrace internals
35mImproving Bpftrace Reliability
25mKernel tracing with BPF
32mBPF: Introduction, Programming Tips and Tricks
21mPerformance Wins with BPF: Getting Started
40mPanel Discussion: eBPF: A New Era in Cloud Infrastructure Tools
38meBPF for Observability: Hard Truths and Practical Wins