Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network usage breakdown #21

Open
erezh16 opened this issue Oct 11, 2020 · 2 comments
Open

Network usage breakdown #21

erezh16 opened this issue Oct 11, 2020 · 2 comments

Comments

@erezh16
Copy link

erezh16 commented Oct 11, 2020

Looks like a great start!

My two cents:
Something that is currently missing from all GUI system monitors in Linux (but exists at a limited level in Win10) - a real, working and useful network usage breakdown:

  1. Per process (matching the current process list)
  2. Per process group (e.g., container)
  3. Per connection target (e.g., "facebook.com")

Also, a display of all registered sockets/handles (lsof style) in their current state, broken down to process or target, would be very useful.

@MatthiasSchinzel
Copy link
Owner

Thank you for your comment!

There will be definitely a redesign of the process tab! This tab could be so much more useful than it is right now and I think your ideas would be a great addition.

@KrispyCamel4u
Copy link

Looks like a great start!

My two cents:
Something that is currently missing from all GUI system monitors in Linux (but exists at a limited level in Win10) - a real, working and useful network usage breakdown:

1. Per process (matching the current process list)

2. Per process group (e.g., container)

3. Per connection target (e.g., "facebook.com")

Also, a display of all registered sockets/handles (lsof style) in their current state, broken down to process or target, would be very useful.

These ideas are great and useful, but the Linux kernel doesn't store the process-wise network information.
To show the process-wise network activity nethogs can be used which basically monitors every process and check how much data is the process receiving and sending. This indeed works good but is a heavy workload on CPU.
This project https://github.com/rejuce/LikeTaskManager does use nethogs.
So it for low end machine this approach is not suitable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants