[ENH] - Consider adding "running" indicator on landing page

[kcpevey]

Feature description

It would be nice to have a reminder when I'm on the landing page that I still have a JupyterLab server running. The landing page is "home base" so I expect it to be a central hub of information. For JupyterLab, a critical piece of information is the fact that its running (and consuming resources).

I know the landing page is generic for all software packs so I'm not sure this is even possible.

Value and/or benefit

Users can use the landing page as a central location for information and could immediately see that they have a server running consuming resources.

Anything else?

No response

[viniciusdc]

Hey @kcpevey, I think this is valuable feedback, and I agree that making this type of information available to users from the landing page would be important. It should be feasible; we would just need to properly format the relevant field under the Nebari App definition so the landing page backend can consume and expose it.

What I am less certain about is the best way to present this in the UI. It could be shown as another item in the list, but I would like to preserve the parent-child relationship with the data-science JupyterHub service. I am not yet sure what the best representation for that would be on the dashboard. @jbouder, what do you think?

One point I would like to discuss with the team is that, at least for the example use case described here, this overlaps somewhat with the alternative JupyterHub apps landing page, where the “running” status is already displayed.

That said, I still think this is a very useful discussion, especially for future child services that may be introduced through packs.

[viniciusdc]

@kcpevey do you mind moving this issue to the landing page repo instead, this conversation belongs there.

[jbouder]

Hey @kcpevey, I think this is valuable feedback, and I agree that making this type of information available to users from the landing page would be important. It should be feasible; we would just need to properly format the relevant field under the Nebari App definition so the landing page backend can consume and expose it.

What I am less certain about is the best way to present this in the UI. It could be shown as another item in the list, but I would like to preserve the parent-child relationship with the data-science JupyterHub service. I am not yet sure what the best representation for that would be on the dashboard. @jbouder, what do you think?

One point I would like to discuss with the team is that, at least for the example use case described here, this overlaps somewhat with the alternative JupyterHub apps landing page, where the “running” status is already displayed.

That said, I still think this is a very useful discussion, especially for future child services that may be introduced through packs.

My suggestion would be to use the Status column. In this case JupyterHub would change from Heathly to Running. This should require no frontend changes, just some updates to the backend.

[viniciusdc]

This has been discussed today, and opened a nice new enh to the landing page, I will open a follow up issue with the necessary next steps