Node Dashboard (UI/UX Feedback)

+1

Understandable per satellite information is important, but the effort for checking if everything is OK should be as minimal as possible. Aka 1 page load, 1 look

1 Like

Refresh data with an ajax request once a minute for a live view, instead of having to manually refresh as it is now?

1 Like

This may be a duplication, but I’d be great to have separated egress and ingress bandwidth used in total as well as per satellite.

Few Ideas:

  • I liked the Audit rate and node uptime %'s in a previous build. That was a quick way to check if everything was ok.

  • If it’s possible to add in a simple link or notification when it’s updated
    (i.e. a simple “Docker image updated on [insert date], here’s a link to the Changlog [insert Github Link]”)

  • The ability to show/hide elements of the dashboard, and break out all the different data ingress egress values.

  • The ability to show monitor log for serious “error” messages ( but filter out all the “untrusted peer” messages, so that only errors which affect the node are displayed. )

2 Likes

All the points for the next iteration are very nice!
In addition to the bandwidth graph Id like to see totals for ingress and egress of my node over current month. Without it its hard to guess the potential earnings from the “bandwidth used” as considerable part could be ingress traffic.

I love the updates in your screenshot, specifically:

  • Human readable names for the satellites
  • Switch to TBm for disk usage
  • Better descriptions for uptime and audit scores

I have a few questions though:

  • Do the score percentages mentioned still reflect the total uptime and audit successrate over the lifetime of the node? If so, the use of the term “score” is a little confusing. If not, don’t use a % sign as the scores are not a percentage.
  • Do the bars represent the actual score or is this just a visualization of the same percentage?

What I would like to see:

  • Please also display the node ID of the satellite somewhere. This helps with connecting ID’s we see in the logs with satellite names shown on the dashboard.
  • This is not visible in the mockup, but usually the amount stored on your node doesn’t change much over the course of the month. So the disk space used graph is almost always a straight horizontal line. It would be nice to change the bottom value of the y-axis dynamically so we can actually see some movement on that graph. You would have to omit the current day for this to work though, since during the day it will be much lower than previous days. This is a little misleading anyway since the graph always looks like you suddenly lost data on the current day.
  • While I like the separate lines for normal repair and audits, in practice the repair and audit lines will always be a straight horizontal line at effectively 0, since normal bandwidth is always several orders of magnitude bigger. Instead this graph is perhaps better used for splitting out egress and ingress.
  • Instead of GBh, show GBd (Gigabyte * days) for the daily numbers in the graph. This would align with the average stored for that day and make more sense to end users.
  • Dynamically switch units between MB, GB, TB, PB etc. Currently we see very large numbers for GBh. (Same goes obviously for GBm, GBd etc)
  • Show totals for uptime score and audit score on the “all satellites” page. Especially for all time percentages and last failure, which can easily be calculated across satellites. I realize that the actual scores are very satellite specific, if the bars are based on this you could either omit them or show the lowest score. (I would prefer showing the lowest score)
  • Add $ amounts and make my earnings calculator obsolete :slight_smile:
  • Include a drop down to select the month (look up data for historic months). Payouts arrive throughout the next month and by that time the dashboard shows data for the next month and we have no easy way to verify. (Even my earnings calculator has to omit payouts for storage since historic data for that isn’t kept in the info.db)
  • If possible show payout transactions based on wallet address on the dashboard. On satellite specific pages show only payouts for that satellite. (I realize that last part will take some added info in the transaction metadata)
  • If the storage directory shows the path inside the container, it may be best to omit it for now as that can be confusing for the end user.
5 Likes

This is unfortunately not possible for technical reasons atm, according to the dev working on the dashboard whom I asked about this.

1 Like

is it possible to use that update now or we have to wait next beta version?

1 Like

If you’re talking about the image, that’s a design mockup. I doubt there is working code yet.

1 Like

Python + selenium = auto refreshing browser :stuck_out_tongue_winking_eye:

I’d love:

  • a vetting status indicator pr. sattelite
  • a histogram of failed audits/uptimes color-coded by satellite
    (so you can guess/tell if you were unreacheable, or only the single satellite)
  • the storage/TBm as a stacked graph, so you can tell which satellite holds the data - and be able to click, to see the page and stats for that satellite in particular.
2 Likes

i’d like a dark mode

3 Likes


1 Like

1 Like

I noticed this as well. As you suggested, not showing the current day would work. Another option would be to prorate today’s value (multiply it by elapsed_seconds_in_day / 86400).

Doh! :slight_smile:

I’m hardly on the individual satellites pages, I tend just to check the “all satellites” page.

Sorry for misunderstanding, this is great feature, but my comment was about total number for current month for egress and ingress separated just like in cli-mode dashboard.

Looks great all of it. Thanks for the insight.

Most of my ideas were already covered by our speedy @BrightSilence :slight_smile:

However, I’d like to stress the point of visualising reputation data - as this is soo critical to any SNO - and the numbers (at least to me) are still a little fuzzy, a running-month/week/hour reputation change would be very useful, as well as the total lifetime of cause.

So now we have rolled over to a new month then there appear to be some bugs.

Particularly as it says I have used 46% of my 25TB limit for the month.

Disk space used also appears to be giving some strange numbers

A thought here…

Is the Bandwidth Remaining actually a nodes “total - already stored data” ?
This could be reasonable if a reserve for transferring all of it’s data to other nodes would be needed?