Resource monitoring plugin enhancements
Is your enhancement related to a problem? Please describe
The resource monitoring plugin is valuable shows to developers CPU and memory usage in their cloud-based developer environment. That has a lot of value because CPU and memory requirements are hard to specify when developing an application but there is still room for improvements here.
Describe the solution you'd like
Here are a few possible enhancements:
Status bar enhancements
- [ ] Status bar shows memory % but not CPU %. Either align CPU with memory or show the % (limit/used) for both only.
- [ ] On hover message should be: "Workspace resources usage. Click for details".
- [ ] When the backend does not provide metrics, on hover message should be: "Metrics server is not running"
details view enhancements
- [ ] Add the CPU and memory requests (now only usage and limit are shown)
- [ ] Add workspace pod totals (memory/cpu usage/requests/limits)
- [ ] Add the namespace cpu and memory quotas (if they exist)
- [ ] Update the metrics values in real time
- [ ] Add a checkbox to hide "non user" containers (machine-exec, jwt proxy, plugins sidecars)
- [ ] Clicking on one entry should open the pod definition yaml or, when running on OpenShift, the console Pod page.
Related issues
- [x] https://github.com/eclipse/che/issues/21518
- [x] https://github.com/eclipse/che/issues/20768
- [ ] https://github.com/eclipse/che/issues/21624
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.