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

[POC] Access to the workspace containers logs #15134

Closed
skabashnyuk opened this issue Nov 6, 2019 · 2 comments
Closed

[POC] Access to the workspace containers logs #15134

skabashnyuk opened this issue Nov 6, 2019 · 2 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Nov 6, 2019

Is your task related to a problem? Please describe.

All logs of the workspace lifetime should be persisted and available to the end-user.

Describe the solution you'd like

The goal of this task is to provide some idea, direction on the way

  • how to keep a history of the latest 5 startups of the workspace
  • how to collect and store logs from different containers of workspace
  • how to provide access for consumers: chectl and dashboard.

Describe alternatives you've considered

n/a

Additional context

#15047

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. team/platform labels Nov 6, 2019
@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Nov 6, 2019
@skabashnyuk skabashnyuk modified the milestones: Backlog - Platform, 7.8.0 Jan 14, 2020
@skabashnyuk skabashnyuk assigned sparkoo and unassigned sparkoo Jan 14, 2020
@sparkoo sparkoo self-assigned this Jan 15, 2020
@sparkoo
Copy link
Member

sparkoo commented Jan 23, 2020

mail list thread about possible technical solutions initiated on che-dev https://www.eclipse.org/lists/che-dev/msg03526.html

@sparkoo
Copy link
Member

sparkoo commented Jan 29, 2020

output of this issue is implementation plan with #15834, #15835, #15836, #15837. Described in epic's #15047 description. Closing this one.

@sparkoo sparkoo closed this as completed Jan 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants