Hello, first and foremost, thank you for writing such a nice system monitor!
One thing that would be helpful for me is for the network traffic graph to show an upload line and a download line for each network interface, much like how the CPU graph shows each core individually. It would also be nice to have a CLI arg that told btm to ignore internal network traffic Iike loopback and docker/vm bridges.
As I type this I'm building a docker image, which involves pulling a huge tarball from the cloud, which manifests in btm as the TX and RX histogram lines being duplicate of each other (with different scaling factors) since it registers the traffic as a download from my wifi adapter's perspective (wlp4s0), and an upload from docker's network bridge perspective (docker0), and I'm betting that the reason for the different scaling factor is that it's also registering the traffic that looks like a download from inside the docker container (since the kernel is shared). Taken together, this means that neither histogram line gives me an accurate understanding of my usage of the broader network, nor the data flowing around internally.
Anyway, keep up the great work, you're a real boon to the rust ecosystem!
Describe the feature request
Hello, first and foremost, thank you for writing such a nice system monitor!
One thing that would be helpful for me is for the network traffic graph to show an upload line and a download line for each network interface, much like how the CPU graph shows each core individually. It would also be nice to have a CLI arg that told
btm
to ignore internal network traffic Iike loopback and docker/vm bridges.As I type this I'm building a docker image, which involves pulling a huge tarball from the cloud, which manifests in
btm
as the TX and RX histogram lines being duplicate of each other (with different scaling factors) since it registers the traffic as a download from my wifi adapter's perspective (wlp4s0), and an upload from docker's network bridge perspective (docker0), and I'm betting that the reason for the different scaling factor is that it's also registering the traffic that looks like a download from inside the docker container (since the kernel is shared). Taken together, this means that neither histogram line gives me an accurate understanding of my usage of the broader network, nor the data flowing around internally.Anyway, keep up the great work, you're a real boon to the rust ecosystem!