Ticket #1387 (new)

Opened 3 years ago

Last modified 22 months ago

Nodewatcher node page should have simple and advanced view

Reported by: valentt Owned by: kostko
Priority: normal Milestone:
Component: nodewatcher/modules Version:
Keywords: Cc:
Related nodes: Realization state:
Blocking: Effort: normal
Blocked by: Security sensitive: no

Description

Currently there are too many graphs and most people who deploy nodes are overwhelmed by amount of data and graphs that are shown node page.

How about also having simple and advanced view?

Simple view would show only most essential info and most essential graphs. This way it would be much more useful and not confuse people.

Attachments

client count.jpg (53.8 KB) - added by slavkokukec 3 years ago.

Change History

comment:1 Changed 3 years ago by valentt

  • Summary changed from Node view should have simple and advanced view to Nodewatcher node page should have simple and advanced view

comment:2 Changed 3 years ago by valentt

My suggestion would be to remove all OLSR and Babel graphs from default (simple) view and to have graphs in this order:

  1. Client count
  2. TX/RX graphs
  3. Memory graph
  4. Babel and OLSR neighbours
Last edited 3 years ago by valentt (previous) (diff)

Changed 3 years ago by slavkokukec

comment:3 Changed 3 years ago by slavkokukec

I agree with Valent that for most users too graphs, which greatly complicate load the page itself.
Interesting and good graph as "client count" in recent times not recorded and shows the results,
I noticed that on some points of the graph "client count" (siemens sx763) is decommissioned from 29.3. Attached is a picture.

comment:4 Changed 3 years ago by mitar

Yes, I completely agree that this node registration process should be improved and made more user friendly. I will be looking into this at some point.

About clients, I very dislike that we are not collecting that stats well. We should really prioritize this because this is the important number to show around. We should collect both DHCP and station data, display it in graphs, and then have also global stats working again. This I think should really be top priority to get it working (and reprocess all old client data which we might have but are not showing in clients graphs).

comment:5 Changed 22 months ago by valentt

Agreed, showing client data is really important.

Note: See TracTickets for help on using tickets.