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

Make Che with debug flag use default log level instead of debug log level #2272

Closed
garagatyi opened this issue Aug 31, 2016 · 7 comments
Closed
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@garagatyi
Copy link

Debug mode of Che enables debug log level of Che java application. This level of debug is almost never used. It can produces tens of gigabytes of logs in several days.

It would be better to allow debugging of Che when debug mode is enabled by leave log level unchanged.
Then debug log level with debugging can be set with another flag , e.g. -dd instead of -d

Che version: Che 4.7.0
OS and version: Ubuntu 14.04
Docker version: docker 1.12
Che install: Linux native

  • Problem started happening recently, didn't happen in an older version of Che: [No]
  • Problem can be reliably reproduced, doesn't happen randomly: [Yes]
@bmicklea bmicklea added the kind/enhancement A feature request - must adhere to the feature request template. label Sep 5, 2016
@bmicklea
Copy link

bmicklea commented Sep 5, 2016

@garagatyi who should this be assigned to for effort estimation? Please take it yourself or assign to a team lead to assess.

@garagatyi
Copy link
Author

@TylerJewell are you ok if I change behavior of --debug flag of che.sh to not change debug level and just start tomcat in debug mode?
It will still be possible to change log level with -l:level, --logs_level:level syntax.

@garagatyi garagatyi self-assigned this Sep 5, 2016
@TylerJewell
Copy link

I do not understand the request. The che.sh file that is in the root of the reps outcry does not have a --debug flag as part of it. Can you be more explicit on what is being proposed?

Note that customers are not encouraged to run Che server natively - so any embedded Che server alterations also affects how the che-server container must operate and be configured

@garagatyi
Copy link
Author

ok, then, please, explain your vision on which way you are encouraging to use for development of Che and how to debug Che without changing default logging level.

@TylerJewell
Copy link

The only acceptable use of Che is through the Che-launcher, which calls the che-server container.

When using Che launcher users can have the che-server use a local binary by setting env variable pointing to its location.

I don't have a vision for how the Che server should be changing its logging level. But if it is to be done then it should only through use of env variables passed into the che-server container. Please draft specification of how it should work and exactly which parameters should be set

@garagatyi garagatyi removed their assignment Sep 8, 2016
@bmicklea
Copy link

bmicklea commented Sep 8, 2016

@garagatyi when an issue is closed please add the milestone label. If the issue has been closed for some reason other than a code commit please clarify the reason for closing.

@garagatyi garagatyi added this to the 5.0.0-M1 milestone Sep 9, 2016
@garagatyi
Copy link
Author

It was fixed. I added the milestone.

@bmicklea bmicklea mentioned this issue Sep 13, 2016
57 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

3 participants