Show the traffic history (bytes), do not clear UI

[maxdobeck]

I'd like to start bandwhich in a special mode that keeps past connections in the UI and lists the bytes up/down by Remote address and Process name. Something closer to the wireshark UI or this iftop cli but for bytes transferred.

I want to see everything scroll past and get bumped out of the UI panel(s) as it reaches the bottom of the panel. So I could look and see the number of bytes uploaded/downloaded by process and remote address.

Or see the traffic sorted by bytes received and only show the top 10 or some reasonable default.

I.g. on linux

$ sudo bandwhich --bytemode

Remote Address
remote | bytes rec | bytes sent
----------------------------------------
some-ec2      123             100
some-host    1204           190

Process Name
process | bytes rec | bytes sent
----------------------------------------
firefox      123             100
chrome    1204           190

In a similar vein to this issue, but introducing an entirely new use: #14

[imsnif]

Hmm... how about adding a "total bytes" to the UI? (assuming it doesn't make it too cluttered)

[maxdobeck]

As a fourth panel? Or as an additional column in one of the existing UI panels?

[imsnif]

I'd say an additional column, if we manage to find space for it in the UI :)

[maxdobeck]

Part of my "problem" is I the traffic I see on my laptop is very brief. So without a sustained connection like a download of a file I can't get at good idea of what's flashing quickly on screen.

Bytes IN/OUT is more of a means to an end in my use-case (although I would like to see that). Really I want to see the process and remote address "stickied" to the UI so they're not just quickly flashing onscreen. Really this is an extension of issue #14

[imsnif]

Right, I agree it's not a good experience right now. Ideally, I would like to solve this with #14. I feel that the more features we add, the less accessible the tool becomes. So what do you think of us trying to solve this with #14 - that should give you a good few seconds to figure out what's going on and should be much more comfortable?
If #14 doesn't do the trick for you, we can revisit this issue. What do you think?

BTW - I know it's less convenient, but for now you can use the --raw flag and parse it somehow to see things a little clearer.

[maxdobeck]

That works for me, I didn't want to make a pull request adding bloat to the cli args. Nor did I want to split the UI and make a whole new panel(s) just to show the bytes in/out. Regardless of issue #14 it would be nice to see the byte total but perhaps that should be tackled later, this feels pre-emptive.

I agree, this should be revisited after #14

[imsnif]

Hey @maxdobeck - we just released 0.9.0 which includes #14. If you still feel the need for something like this, I'd be happy if you'd write up a proposal in a new issue.
I hope the tool feels better for you now. :) Would love to hear further comments and suggestions (or of course receive contributions).