Che plugin broker should persist logs.
See original GitHub issueIs your enhancement related to a problem? Please describe.
Currently, it is quite difficult to get logs from the Che plugin broker, apart from what is printed to the output in the workspace panel. The broker is deleted right after it finishes, which means viewing the full logs often requires catching it in a quite short window. Additionally, it’s not currently possible to view logs from the init broker without accessing them directly.
Describe the solution you’d like
The Che plugin broker should also write its logs to a file in /workspace_logs
, which is already mounted at startup. This would make it easier to get information from a previous run if there are any issues.
Describe alternatives you’ve considered
Since plugin broker is in flux and may be reworked significantly, it may not be worth putting time into this.
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
[Doc] Viewing plug-in broker logs · Issue #14363 · eclipse/che · GitHub
The logs from the plug-in broker are not persisted. As the pod itself is deleted very quickly, events will in most cases be...
Read more >Re: [che-dev] How to collect and persist all workspace logs? - Eclipse
- I'd like to make it configurable, so it can be completely disabled with some configuration flag, because it might be quite heavy...
Read more >How to repackage a Visual Studio Code extension into a Che ...
I simply want to add my plugin as third-party. It is straightforward by defining the meta.yml file. However, if I avoid using dependencies...
Read more >Chapter 2. Retrieving CodeReady Workspaces logs
This section describes how to log the exchange between Che-Theia and a debug adapter into the Output view. Prerequisites. A debug session must...
Read more >eclipse/che-plugin-metadata-broker - Quay.io
This broker must be run prior to starting the workspace's pod, as its job is to provision required containers, volumes, and environment variables...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Well, it’s not really clear how then access workspaces logs… Some additional pod is needed just to read that logs. I think that debug mode should satisfy our needs regards get workspace-logs About devworkpace controller - storing logs will not help because:
So, I would close this issue and later when it becomes critical - create a new one for controller and solve it in possible for that case, like k8s events, propagate pods logs as workspace logs if or whatever is possible. @amisevsk WDYT?
Makes sense to me. The original concern was for non-ephemeral workspaces, where the broker already mounts the workspace volume (in order to store plugins). The goal was to have the artifacts broker log to a file as well as to
stdout
.