Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resource monitoring plugin enhancements #20809

Open
2 of 12 tasks
Tracked by #21615
l0rd opened this issue Nov 23, 2021 · 2 comments
Open
2 of 12 tasks
Tracked by #21615

Resource monitoring plugin enhancements #20809

l0rd opened this issue Nov 23, 2021 · 2 comments
Assignees
@svor @vitaliy-guliy @vinokurig
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Nov 23, 2021 •
edited by svor
Loading

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

image

  • 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

image

  • 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
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 23, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 23, 2021
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. area/plugins and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 23, 2021
@svor svor mentioned this issue Aug 8, 2022
Closed
67 tasks
@Divine1 Divine1 mentioned this issue Aug 22, 2022
Closed
@svor svor mentioned this issue Aug 27, 2022
Closed
82 tasks
@azatsarynnyy azatsarynnyy mentioned this issue Aug 30, 2022
Closed
@che-bot
Copy link
Contributor

che-bot commented Mar 7, 2024

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2024
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2024
@che-bot
Copy link
Contributor

che-bot commented Dec 22, 2024

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 22, 2024
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svor svor

@vitaliy-guliy vitaliy-guliy

@vinokurig vinokurig

Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
Red Hat OpenShift Dev Spaces and Web Terminal Priorities
Status: No status
Milestone
No milestone
Development

No branches or pull requests
6 participants
@nickboldt @l0rd @svor @vitaliy-guliy @vinokurig @che-bot