1. posterid:1132473
  2. Three audiences

Three audiences

Brendan Gregg
 

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.
B) Sysadmins/operators/senior devs (~5k): who will use the existing bcc tools (and edit some).
C) Everyone else (>50k): via dashboards/GUIs.

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.

Audience A might be served by something like ply, or partially served by Sasha's multi-tools.

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).

I did file this for Intel snap: https://github.com/intelsdi-x/snap/issues/800 . Sounds like they may need our help. We should also file something similar for collectd... What else?

Brendan
Join iovisor-dev@lists.iovisor.org to automatically receive all group messages.