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

Archive logs on che-server #15836

Closed
sparkoo opened this issue Jan 27, 2020 · 1 comment
Closed

Archive logs on che-server #15836

sparkoo opened this issue Jan 27, 2020 · 1 comment
Labels
area/che-server 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

@sparkoo
Copy link
Member

sparkoo commented Jan 27, 2020 •
edited
Loading

Is your enhancement related to a problem? Please describe.

To improve workspace diagnosis capabilities, we should archive logs of latest 5 startups of the workspace.

Describe the solution you'd like

  • design API on che-server that will receive the logs from just-stopped workspace from LogCollector(Create LogCollector component #15835)
  • use this API from LogCollector as a backend
  • persist the logs on che-server with all metadata (datetime, workspaceid, userid, ...?)
    • currently existing and possibly easiest solution is to use postgres. It is still open question, but to respect future architecture direction, we must ensure that another storage could be later implemented and not hard-wire to only one implementation.
    • requirements are to store latest 5 workspace runs. It would be nice to have it configurable. Also we might need to limit physical size of the logs.
    • Workspace logs should be deleted with the workspace ❓

Describe alternatives you've considered

  • persist on dedicated PV in workspace's namespace
  • persist on dedicated PV in che-server namespace
  • came up with new service responsible to archive and provide logs

Additional context

#15047
@sparkoo sparkoo added the kind/enhancement A feature request - must adhere to the feature request template. label Jan 27, 2020
@sparkoo sparkoo mentioned this issue Jan 27, 2020
Closed
@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 Jan 27, 2020
@sparkoo sparkoo removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 27, 2020
@sparkoo sparkoo mentioned this issue Jan 27, 2020
Closed
@skabashnyuk skabashnyuk mentioned this issue Jan 27, 2020
Closed
12 tasks
@sparkoo sparkoo added area/che-server severity/P1 Has a major impact to usage or development of the system. team/platform labels Jan 27, 2020
@sparkoo sparkoo mentioned this issue Jan 29, 2020
Closed
@sparkoo
Copy link
Member Author

sparkoo commented Feb 11, 2020

replaced with #15983 to more details see this mailing list thread https://www.eclipse.org/lists/che-dev/msg03526.html

@sparkoo sparkoo closed this as completed Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-server 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
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sparkoo @che-bot