Request for feedback - UI dashboard

We’re planning to redesign the Mender UI dashboard a bit to improve the quality and scalability of the information displayed on it. A lot of the current dashboard data is duplicating what’s in the deployments tab and it could be a lot better.

I would really appreciate some feedback from Mender users about what you’d like to see on the dashboard, what information is important/urgent for you to know every time you log in to the UI. Some suggestions:

  • If there are pending devices
  • If the number of accepted devices has changed recently - have any been accepted or removed since your last login?
  • If any deployments have completed recently/since your last visit
  • If there are deployments in progress
  • If there are deployments pending
    • Q: how long can a deployment stay in ‘pending’ status before you start to think something is wrong?
  • Show status of your most recent deployments - for example the status all created today & yesterday (and even longer back? 3 days?)

Do these sound useful, is anything missing? What do you look for first when you use the Mender UI? What would events would you want to be notified about?

Your comments would be very valuable!

1 Like

Your suggestions sound useful. I’m not sure about the actual implementation but I think it might be useful to have a quick overview on the dashboard of the number of devices that have heartbeated recently and the number of devices that haven’t heartbeated in X amount of time.

3 Likes

Currently, all the devices are listing on the server based on either the device ID (which server assigned) or the MAC ID (specifically Ethernet MAC ID).


There are some cases, where the device might not have an Ethernet connection (it may have a Wi-Fi or LTE connection instead).
We know how to get the required information by changing the script on the device.
But, I would like to know whether any custom option can be given on the server (apart from the MAC ID device ID) to name it as what we required?

@WeZzyNL that’s a good suggestion. I would also like to show that on the dashboard - something like “X devices may be offline” if they haven’t heartbeated in user-selected amount of time. And then click through to be taken to view those devices. What sort of timeframe would be a sensible default in your opinion?

1 Like

Not on the server as it stands, but you are able to configure the device identity on the client - https://docs.mender.io/1.7/client-configuration/identity - but I think that might be what you are referring to.

This topic was more about the dashboard tab on the GUI, the first page you see when you load it up - if there was some information you would want to see on that page to get an at-a-glance overview of your devices/deployments, before you dig in to details.

1 Like

First, I would like to thank you for a great product. I agree with the above folks, a status of connected clients by group would be No. 1.

The rest would be nice to help with problem clients…

Average time to complete and verify successful updates. We have devices that turn off at night. It would be nice to know the latest time we can update based on the average update time.

No. of retry attempts for updates if greater than one. – Again show’s problem locations as we are geographically spread. Showing if there are issue in smaller community where bandwidth is limited.

No. of successful updates for the month by group.

Bandwidth usage especially during updating.

1 Like

@gil0109 Thanks! That’s very helpful.

We’re about to add a basic feature on the dashboard that alerts you when clients haven’t pinged in 24 hrs - we will iterate over this and make the length of time customizable too.

Some of other features you suggest sound super interesting, and might mesh well with an idea for per-device update history that we have in mind.

(On a side note, if bandwidth usage is an issue for you then Update Modules might be interesting to you!)

1 Like

hi,
i am not aware of an option in the dashboard to do an deployment at a certain time or at least did not find it, but this would be nice to lets say for example 01:00 am push some deployments to devices.
is this possible at all? with or without the dasboard?
anyway this would be a nice option to have :slight_smile:
greets

They way you would implement something like this today is on the client utilizing state-scripts which allow you control the update flow, here you can say, only start downloading the artifact if it is after 01:00, or you can download it but do not reboot until time is 01:00 and so on.

1 Like

I personally would like the ability to group devices (for both monitoring and releases) by one of Inventory fields, and make these groups dynamic (as inventory is). I understand it is possible by using API but having this out-of-the box would be cool!

And a couple of comments regarding today’s UI:

  • Deployments view shows deployments of the last day by default and no quick way to show all deployments.
  • impossible to create a deployment for a number if individual devices

As for proposition for dashboard, It would be nice to have a system overview where you can see the percentage of all software verions deployed in your system