"Sysdig and Falco now powered by eBPF" too; <a href="https://sysdig.com/blog/sysdig-and-falco-now-powered-by-ebpf/" rel="nofollow">https://sysdig.com/blog/sysdig-and-falco-now-powered-by-ebpf...</a><p>- "Linux Extended BPF (eBPF) Tracing Tools" <a href="https://www.brendangregg.com/ebpf.html" rel="nofollow">https://www.brendangregg.com/ebpf.html</a> lists eBPF commands, [CLI] frontends, relevant kernel components<p>- awesome-ebpf#manual-pages <a href="https://github.com/zoidbergwill/awesome-ebpf" rel="nofollow">https://github.com/zoidbergwill/awesome-ebpf</a> links to the kernel eBPF docs<p>- eBPF -> BPF Berkeley Packet Filter: <a href="https://en.wikipedia.org/wiki/Berkeley_Packet_Filter" rel="nofollow">https://en.wikipedia.org/wiki/Berkeley_Packet_Filter</a> :<p>> Extensions & optimizations: <i>Since version 3.18, the Linux kernel includes an extended BPF virtual machine with ten 64-bit registers, termed extended BPF (eBPF). It can be used for non-networking purposes, such as for attaching eBPF programs to various tracepoints.[5][6][7] Since kernel version 3.19, eBPF filters can be attached to sockets,[8][9] and, since kernel version 4.1, to traffic control classifiers for the ingress and egress networking data path.[10][11] The original and obsolete version has been retroactively renamed to classic BPF (cBPF). Nowadays, the Linux kernel runs eBPF only and loaded cBPF bytecode is transparently translated into an eBPF representation in the kernel before program execution.[12] All bytecode is verified before running to prevent denial-of-service attacks. Until Linux 5.3, the verifier prohibited the use of loops.</i><p>- ... EVM/eWASM opcodes have a cost in gas/particles; <a href="https://github.com/crytic/evm-opcodes" rel="nofollow">https://github.com/crytic/evm-opcodes</a> ... (dlt) Dataset indexing curation signals & incentives<p>"Tracing in Kubernetes: kubectl capture plugin." <a href="https://sysdig.com/blog/tracing-in-kubernetes-kubectl-capture-plugin/" rel="nofollow">https://sysdig.com/blog/tracing-in-kubernetes-kubectl-captur...</a><p>kubectl-capture: <a href="https://github.com/sysdiglabs/kubectl-capture.git" rel="nofollow">https://github.com/sysdiglabs/kubectl-capture.git</a><p>Is it possible to do this sort of low level distributed tracing with Pixie e.g. conditionally when a pattern expression matches?