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

Display the running workspace containers logs in the che-theia output view #19942

Open
sunix opened this issue Jun 8, 2021 · 1 comment
Open

Display the running workspace containers logs in the che-theia output view #19942

sunix opened this issue Jun 8, 2021 · 1 comment
Labels
area/plugins 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.

Comments

@sunix
Copy link
Contributor

sunix commented Jun 8, 2021 •
edited
Loading

Is your enhancement related to a problem? Please describe.

When a che workspace is starting, we can see the logs of each container

  • for the dev: by turning on the debug mode.
  • for the admin: by going back to the openshift console, kubernetes console or using kubectrl

the problem is that the logs are not available anymore once the workspace has switched to che-theia for the dev.

Describe the solution you'd like

It would be nice to have the log output of each container of the workspace in the output view
one entry for each, name prefixed with workspace-container-.
For instance: workspace-container-vscode-quarkus3rk for the logs of the vscode quarkus sidecar

Selection_392

Describe alternatives you've considered

N/A

Additional context

N/A
@sunix sunix added the kind/enhancement A feature request - must adhere to the feature request template. label Jun 8, 2021
@sunix sunix changed the title Display the containers logs in the che-theia output view Display the running workspace containers logs in the che-theia output view Jun 8, 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 Jun 8, 2021
@skabashnyuk skabashnyuk added 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 Jun 8, 2021
@che-bot
Copy link
Contributor

che-bot commented Dec 6, 2021

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 6, 2021
@sunix sunix 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 Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/plugins 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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sunix @skabashnyuk @che-bot