But we haven't spoken much about audience C, which will end up the biggest. And that will include most of the developers at Netflix (I think only a few of us are going to ssh onto instances and run the bcc tools, even though we install them by default now).
Audience A might be served by something like ply, or partially served by Sasha's multi-tools.
I'm pretty happy with where the toolset is for audience B. There's a few more tools I'd like to add (TCP internals and buffering, disk I/O internals), but a lot can be done now.
C) Everyone else (>50k): via dashboards/GUIs.
B) Sysadmins/operators/senior devs (~5k): who will use the existing bcc tools (and edit some).
As discussed on the call, here's who I think are the three audiences for bcc/BPF tracing:A) Kernel hackers (~100): who would like the language to be easier, better errors, docs, etc.