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.

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

Show warning notification in CheCode if >90% of the resource limit is reached #21624

Open
Tracked by #20809
dkwon17 opened this issue Aug 8, 2022 · 2 comments
Open
Tracked by #20809
Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@dkwon17
Copy link
Contributor

dkwon17 commented Aug 8, 2022

Is your enhancement related to a problem? Please describe

When working on a che-code project, I ran a task which led to the memory usage of my developerment container to exceed the memoryLimit. The VS Code editor stopped responding as a result, so I had to restart the workspace.

Describe the solution you'd like

It would be nice if the che-resource-monitor extension displayed a warning notification if, say, >%90 of the memory or CPU limit has been reached.

Maybe something like:

Warning: 9.43GB out of 10GB memory used by the {CONTAINER_NAME} container.
Consider increasing the memoryLimit for this container.

[Don't show again]

I think there should also be a setting to disable the notification.

Describe alternatives you've considered

No response

Additional context

No response

@dkwon17 dkwon17 added kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system. area/editor/vscode Issues related to the Code OSS editor of Che labels Aug 8, 2022
@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2023

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 Feb 4, 2023
@che-bot che-bot closed this as completed Feb 11, 2023
@dkwon17 dkwon17 reopened this Feb 14, 2023
@dkwon17 dkwon17 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 14, 2023
@che-bot
Copy link
Contributor

che-bot commented Aug 13, 2023

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 Aug 13, 2023
@dkwon17 dkwon17 added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants