options to redirect stdout/stderr in gunicorn logging #1271
Comments
|
I love this idea. I was going to propose it myself after struggling with trying to get Django to have its stderr show up in gunicorn's error.log. I was just about to ask about it on the mailing list, but it seems that lists.gunicorn.org is dead. So yeah, there should be a way to get stdout and stderr from the wsgi app sent to the same places that gunicorn uses for its error logging etc. In this way, it will be like the old days of CGI scripts sending their output to apache log files. :) |
|
It does seem to be causing a lot of confusion. I've answered now a post on SO and I think several questions on our issue tracker about missing log messages. |
|
Making it opt-in seems the best idea. |
Add the new setting `--caapture-stdio` to capture output from stdio/stderr to the current log file. fix #1271
|
@JohnSpeno @tilgovi see the PR above. Should fix the issue. Let me know. |
Add the new setting `--caapture-output` to capture output from stdout/stderr to the current log file. fix #1271
|
Looks good to me. Thank you. |
Add the new setting `--caapture-output` to capture output from stdout/stderr to the current log file. fix benoitc#1271
following a discussion on twitter, I would like to rediscuss having an option to redtirect stdout/stderr to our logs:
This behaviour has been removed in 4152318 3 years ago. But rediscussed last year and now.
I think we could have a
--capture-stdiooption that would allows it. Thoughts?The text was updated successfully, but these errors were encountered: