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 347040 - Multiple Network Interface on Network History Graph
Multiple Network Interface on Network History Graph
Status: RESOLVED OBSOLETE
Product: system-monitor
Classification: Core
Component: resources
2.14.x
Other All
: Normal enhancement
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 535354 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-09 14:56 UTC by cruiseoveride
Modified: 2018-05-22 11:58 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description cruiseoveride 2006-07-09 14:56:19 UTC
Is it possible, just like with the CPU history graph, to be able to display the usage on more than one network card as individual lines on the Netowrk History graph.
That is, if one had 2 network interfaces, the Network History graph would show 4 different lines,eg.
eth0 - TX - Dark Pink
     - RX - Dark Blue
wth0 - TX - Light Pink
     - RX - Light Blue

Just an example, it would really be nice to have this feature. pretty please, with sugar on top :)
Comment 1 Benoît Dejean 2006-07-09 15:09:06 UTC
on the same graph or in multiple graphs just like cpus ?
Comment 2 cruiseoveride 2006-07-09 17:52:53 UTC
like cpus
Comment 3 Robert Roth 2011-11-15 15:13:24 UTC
*** Bug 535354 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2012-02-26 10:46:41 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 GNOME Infrastructure Team 2018-05-22 11:58:19 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/6.