You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current summary data in Jobs view is not very intuitive. Currently it shows, how many groups are running out of total groups in a Job. But people are really interested on whether the desired allocs are running and healthy within a job. Something similar to the below one. This is Job overview from Nomad UI dashboard.
The allocs should be the sum of allocs from each group. (Mostly each job will have one group. I still can’t find a good use case, where we run multiple groups in a Job)
I can give a PR on this change 😎 . Let me know if this improvement make sense.
The text was updated successfully, but these errors were encountered:
Hey @jawahars16,
I thought about the same and I like the idea. The only thing I'm just a little bit concerned about is that people will have to know somehow what the number mean (healthy/running/desired). Probably add it to the readme will be enough. Also at some point it would be nice to have a "help" page where we could add this info as well.
Have you also thought about the coloring? Maybe:
Thanks for the update. A help page would be really nice, which can include this information and other keybindings as well.
Yes colouring is a good suggestion. 👍 I am planning to give a PR on this.
What is the problem?
The current summary data in Jobs view is not very intuitive. Currently it shows, how many groups are running out of total groups in a Job. But people are really interested on whether the desired allocs are running and healthy within a job. Something similar to the below one. This is Job overview from Nomad UI dashboard.
How to solve?
We can show below detail in Summary.
<healthy allocs> / <running allocs> / <desired allocs>
Example
The allocs should be the sum of allocs from each group. (Mostly each job will have one group. I still can’t find a good use case, where we run multiple groups in a Job)
I can give a PR on this change 😎 . Let me know if this improvement make sense.
The text was updated successfully, but these errors were encountered: