[Feature Request] Network Activity/Network History Docklet

Bug #574051 reported by yarly
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Docky
New
Wishlist
Robert Dyer

Bug Description

This feature should be similar in features available by the windows application DU meter
http://www.dumeter.com/

In Gnome, similar functionality is available in the system monitor on the
resources tab under network history which allows you to view real time
network activity and speed. These features are not available in Docky
at the moment.

Revision history for this message
Robert Dyer (psybers) wrote :

Perhaps this can be merged in with the CPU docklet, and make it a more generalized docklet that has CPU, Mem, Network, etc and then settings to pick what you want.

Changed in docky:
importance: Undecided → Wishlist
assignee: nobody → Robert Dyer (psybers)
Revision history for this message
yarly (ih8junkmai1) wrote :

That's what I was thinking.

As it stands right now Gnome allows you to add a System Monitor Applet
to panels. Configuration options for the System Monitor Applet include
the ability to show real time information for CPU, RAM, network, swap,
load, and hard disk activity.

Revision history for this message
Lee Hyde (anubeon) wrote :

I certainly would appreciate an expanded role for the CPU Monitor docklet, perhaps with polling of CPU/GPU/HDD temperatures where appropriate, but wouldn't it be more appropriate to incorporate network activity/history into the Network Manager docklet?

Lee.

Revision history for this message
Matthew Woerly (nattgew) wrote :

If you're planning on making a super system monitor applet with network information as well as CPU loads, sensor temperatures, etc., you should update the title and description to reflect that.

Revision history for this message
Florian Dorn (florian-dorn) wrote :

I finally have created a branch of docky (2.1.1), so I request you to review, commment and hopefully merge it
lp:~florian-dorn/+junk/docky-NetworkMonitor

Revision history for this message
Robert Dyer (psybers) wrote :

Just an FYI, this can not be merged into Docky 2.1.x, only 2.2.x or newer. Thus, you need to branch trunk and not docky/2.1 if you want it to be merged eventually.

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@Florian: To create a mergeable branch do "bzr branch lp:docky", add you changes and push it like this "bzr push lp:~florian-dorn/docky/networkmonitor. Now you can request an actual merge on launchpad. (btw you need to "bzr commit" something)

Revision history for this message
Florian Dorn (florian-dorn) wrote :

Thanks for your patience, and sorry for wasting your time earlier.
So finally, please merge https://bugs.launchpad.net/+branch/~florian-dorn/+junk/docky-NetworkMonitor

Revision history for this message
Robert Dyer (psybers) wrote :

@Florian: hate to be a stickler... but can you name your branch something like 'lp:~florian-dorn/docky/networkmonitor' so that we can do an official merge request/review on the branch?

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

This is partly fixed in trunk bzr1795 with the merge of the NetworkMonitor docklet

Revision history for this message
guerda (derguerda) wrote :

So what exactly means "partly fixed"? Is there a running version of it or do you have to do further integration work?

Revision history for this message
Lee Hyde (anubeon) wrote :

@guarda There's a working version in the latest 2.1 release.

I am a little baffled by the decision not to 'merge' this with the network manager docklet (not that I've seen that docklet in a while, it doesn't appear to be available when using connman as I am) and using hotseating (a'la weather docklet) to reveal upload/download/speed statistics for active network interface(s).

It seems odd to me to separate the two, although am I correct in guessing that the network monitor docklet is (classed as) community developed (which might explain it)?

Revision history for this message
Robert Dyer (psybers) wrote :

@Lee: as you yourself pointed out, the reason is because not everyone uses NetworkManager. The NetworkManager docklet *requires* using NM and does not work with connman (or anything else).

The Network Monitor docklet however just reads from /proc and is independent of what is managing the interface(s).

Revision history for this message
Lee Hyde (anubeon) wrote :

> The NetworkManager docklet *requires* using NM and does not work with
> connman (or anything else).

I wasn't certain that this was the case, as for the first few weeks after switching to connman the NetworkManager docklet still appeared in the preferences dialog. I wasn't sure whether it's disappearance was as a result of my using connman, or whether it had been removed for some QA reason. So thank you for clearing that up. :-)

Incidentally, is there scope (in the long term perhaps) for a 'NetworkManager' style docklet with comprehensive support for NetworkManager, connman and wicd, or would such be impracticable?

> The Network Monitor docklet however just reads from /proc and is
> independent of what is managing the interface(s).

Noted. I do think the design needs a bit of a clean-up though. In my humble opinion* the network monitors dock icon should display a simple graphical metric (up/down arrows with a colour scale similar to that of the CPU monitor perhaps?) of the up/download speed. The name of the network interface and the numerical up/download speed should be displayed ONLY within the tooltip.

It would also be nice if clicking on the icon yielded a graph of historic up/download speeds (presented similarly to the Weather docklet) and (in an ideal world) wireless signal strength (although I recognise that this may be outside of the remit of a stand alone NetworkMonitor docklet).

Kind Regards,

Lee.

*Please don't read these as demands. I'm just presenting my tupence, for what it's worth, in the hope that it may inspire you developers. If I had the skills and time (I'm preoccupied with my M/Phil-Ph.D. transfer report right now) I'd develop a docklet myself.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.