After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 506390 - feature request: display per process network usage/permissions
feature request: display per process network usage/permissions
Status: RESOLVED OBSOLETE
Product: system-monitor
Classification: Core
Component: process list
unspecified
Other All
: Normal enhancement
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 559784 629585 712326 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-12-30 08:51 UTC by mmcg069
Modified: 2018-05-22 12:03 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description mmcg069 2007-12-30 08:51:21 UTC
A couple of ideas i thought worth consideration.

Firstly, a simple up/down display of internet usage on a per process basis.  So if you have a number of applications accessing the internet, you can see how often they are downloading uploading data, and what percentage of your download/upload speed they are attaining.

Could also be useful to detect suspicious activity on the network and associate it with an app or process.

A quick mock-up i made a while back:
http://ubuntuforums.org/attachment.php?attachmentid=47683&stc=1&d=1193265442

Moreover, is their such a thing as networking 'nice'?  Could processes have bandwidth caps/priorities imposed from within g-s-m?  Furthermore, something like a simple firewall or at least a way to permit/deny nwetwork connections for apps/processes could be a good thing for g-s-m to incorporate.  Seems like a logical place at least to include this function.  maybe such a feature-set could live in its own tab within g-s-m, say, 'network activity' or 'network access'?  In summary could some sort of simple firewall capacity be built into g-s-m?  Would this be appropriate?
Comment 1 Benoît Dejean 2008-01-01 12:47:28 UTC
(In reply to comment #0)
> A couple of ideas i thought worth consideration.
> 
> Firstly, a simple up/down display of internet usage on a per process basis.  So
> if you have a number of applications accessing the internet, you can see how
> often they are downloading uploading data, and what percentage of your
> download/upload speed they are attaining.

AFAIK, there's no way to get this information

> Could also be useful to detect suspicious activity on the network and associate
> it with an app or process.
> 
> A quick mock-up i made a while back:
> http://ubuntuforums.org/attachment.php?attachmentid=47683&stc=1&d=1193265442
>

Requires login.

> Moreover, is their such a thing as networking 'nice'? 

No.
Comment 2 bi2h5da02 2009-06-16 20:32:23 UTC
*** Bug 559784 has been marked as a duplicate of this bug. ***
Comment 3 bi2h5da02 2009-06-16 20:36:55 UTC
(In reply to comment #0)
> Moreover, is their such a thing as networking 'nice'?

QoS in your router?  I don't think this really fits in System Monitor.

(In reply to comment #1)
> AFAIK, there's no way to get this information

nethogs does it.  iotop does the equivalent for hard drive access.

Process Explorer for Windows does all of these things.  It would be nice if we had an equivalent in Linux world.

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
 
> Requires login.

http://i44.tinypic.com/jzcnkw.png
Comment 4 André Klapper 2012-02-26 10:46:14 UTC
[Adding missing "QA Contact" entry so system monitor bug report changes can still be watched via the "Users to watch" list on https://bugzilla.gnome.org/userprefs.cgi?tab=email when the assignee is changed to an individual.]
Comment 5 Robert Roth 2013-08-03 12:26:59 UTC
*** Bug 629585 has been marked as a duplicate of this bug. ***
Comment 6 Robert Roth 2013-11-14 19:20:48 UTC
*** Bug 712326 has been marked as a duplicate of this bug. ***
Comment 7 GNOME Infrastructure Team 2018-05-22 12:03:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/18.