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

Docker graylog splits up stacktraces #22979

Closed
justechn opened this Issue May 25, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@justechn

justechn commented May 25, 2016

I am just getting started with docker and graylog and I have run into a snag. Docker is splitting up stacktraces so that each line is a new log. This is not optimal, and makes viewing the entire stack trace impossible.

I setup my docker container from the instructions found here https://www.graylog.org/blog/28-centralized-docker-container-logging-with-native-graylog-integration

Is there some step that I am missing?

here is an example of what I get in graylog
image

@thaJeztah

This comment has been minimized.

Show comment
Hide comment
@thaJeztah

thaJeztah May 25, 2016

Member

Yes, this is the way logging works in Docker; log-entries are separated by newlines, because there's no way for Docker to "detect" if multiple lines should be treated as a "single" log-entry, or as multiple.

See the discussion on #22920 for some background / context.

Unfortunately, I'll have to close this issue, but possibly we can have more features (including this use case), if there's an option to add custom logging-plugins.

Member

thaJeztah commented May 25, 2016

Yes, this is the way logging works in Docker; log-entries are separated by newlines, because there's no way for Docker to "detect" if multiple lines should be treated as a "single" log-entry, or as multiple.

See the discussion on #22920 for some background / context.

Unfortunately, I'll have to close this issue, but possibly we can have more features (including this use case), if there's an option to add custom logging-plugins.

@justechn

This comment has been minimized.

Show comment
Hide comment
@justechn

justechn May 25, 2016

ok, thanks, it sounds like docker logging is not going to work for us. I will look for another solution.

justechn commented May 25, 2016

ok, thanks, it sounds like docker logging is not going to work for us. I will look for another solution.

@mblomdahl mblomdahl referenced this issue Jan 2, 2018

Merged

Feature/Basic log forwarding #165

6 of 6 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment