[LibreQoS] Upcoming UI progress for LibreQoS v1.5-BETA-2

[Frantisek Borsik]

Hello to all,

Sharing some new *UI *mockups with commentary from Herbert. This ongoing
effort is called UI2 and we encourage you all too join our chat for most
up-to-date news on LibreQoS:
https://chat.libreqos.io/join/fvu3cerayyaumo377xwvpev6/

It will be a part of *v1.5-BETA-2* (due in 2-3 weeks if nothing goes wrong)
and will be followed up with *v1.5-BETA-3*: "a greatly *improved LTS*
pipeline to handle the pretty vast amounts of new data we have."

"Playing with ways to visualize flow data."

[image: image.png]

"Now seems like a decent time to talk about a bit of UI2 I'm finding really
exciting to work on: the circuit page.
This is the page you get to when you click on an active circuit, you can
get there lots of ways, fast search, shaped devices list, top N lists,
etc., I'm trying to take it from a science experiment to an actionable,
useful page for support people.
It's not at all complete - the various tins graphs, site location graphs
and things will be back. This is very much a work in progress."

[image: image-2.png]

^^What are we seeing here? At the top:

- We lead in with who you're looking at.
- The, blurred out, circuit name, the parent node, which will take you to
the tree position, speed limits.
- Then a gauge for current - at this second - utilization.
- Then a Total Circuit Throughput graph, showing all devices in this
circuit's combined usage over time.
- Then a graph showing TCP retransmits from all devices.

Going down to the tabs (which will re-add the science experiment stuff!):
-The devices tab shows you each device in the circuit. We lead off with the
MAC, because it's uniquely identifiable, or should be!
- If you have a comment, we show it.
- We list all your IPv4 and IPv6 addresses. If its not a network address, a
background pinger sends 1 ping per second to each item. It gets a red mark
if it never replies, a check mark if it does - and we show ping loss and
ICMP time. These are colorized - I picked a lossy circuit to ensure you
could see it.
- We show you "last seen" - when did the shaper last see some traffic? So
now you have a 2nd chance to see if they are offline.
- We show you throughput as a bar, covering circuit range, no bar just a
number if there's no limit, dividing by zero sucks.
- Up and down are separated.
- RTT readings are shown as a colorized bar, too.
- We show you current, this second, retransmit scores.
- Then to the right we graph throughput by just the device, TCP retransmits
by just the device, and a histogram of the ping times we're accumulating
while you watch.

The "Active Flows" tab gives you a count of data flows in the last second,
and plots them in the Sankey graph above.

There's obviously a crapload more to come. Wanted to share some progress."

"Likewise, if you navigate the tree - you see real time data. You can
expand, click to view just a single segment. Notice that we have
retransmits, Cake marks/drops in there now!"

[image: image-3.png]

"Likewise, clients attached to each tree node are rendered with real-time
data, sorry for the lack of data, I'm only testing on a tiny portion of the
network":

[image: image-4.png]

"Lastly, the dashboard. It defaults to a pretty minimal view, but you can
click the pencil at any time to add/remove/rearrange the dashboard widgets
- from an ever growing selection. Some are more useful than others, some
mostly serve to attract the attention of passers-by.

Here's a crazy zoomed out version with just about everything live updating":

[image: image.png]

"And there are some with which we were just having fun, such as the RTT
histogram with time as a 3rd axis/dimension":

[image: image-2.png]

*Can't wait to share more cool stuff with all of you.*

All the best,

Frank

Frantisek (Frank) Borsik



https://www.linkedin.com/in/frantisekborsik

Signal, Telegram, WhatsApp: +421919416714

iMessage, mobile: +420775230885

Skype: casioa5302ca

frantisek.borsik at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 198188 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image-2.png
Type: image/png
Size: 459511 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image-3.png
Type: image/png
Size: 451367 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image-4.png
Type: image/png
Size: 757981 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 590870 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image-2.png
Type: image/png
Size: 261243 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/libreqos/attachments/20240714/d7673c5c/attachment-0011.png>