-
Notifications
You must be signed in to change notification settings - Fork 498
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
Add an option to send logs to STDOUT #383
Labels
Comments
As a side note, if anyone has the same issue, I personally worked around it with the following supervisord service :
And the following script in
The resulting logs are a bit ugly, but it works. A proper setup probably would prefix log lines by the name of the service they are coming from, or something similar. |
I'd be open for a pull request.
…On Mon, Feb 18, 2019, 10:56 AM Arnaud Venturi ***@***.*** wrote:
When using docker with a container orchestrator (kubernetes, in my case),
most logging infrastructures will expect your containers to send their logs
through STDOUT/STDERR.
In this image, we miss most interesting logs (typically, access logs)
because they go directly to files. Moreover, the location where they go is
a volume, which makes it way harder to symlink the logfiles to another
location (such as /dev/stdout or /proc/1/fd/1).
It would be really convenient to have an environment variable that would
allow all logs to be sent to STDOUT.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#383>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AFWomUGJNZnOchwdAgV-fjSopxGieV4Iks5vOs0wgaJpZM4bBKdA>
.
|
I'll try to make one if I can find some time for that ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using docker with a container orchestrator (kubernetes, in my case), most logging infrastructures will expect your containers to send their logs through STDOUT/STDERR.
In this image, we miss most interesting logs (typically, access logs) because they go directly to files. Moreover, the location where they go is a volume, which makes it way harder to symlink the logfiles to another location (such as
/dev/stdout
or/proc/1/fd/1
).It would be really convenient to have an environment variable that would allow all logs to be sent to STDOUT.
The text was updated successfully, but these errors were encountered: