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

Logs sent to logstash are interpreted as stream and therefore are incorrectly parsed #2

Merged
merged 1 commit into from
May 23, 2013

Conversation

gwhitelaw
Copy link
Contributor

As the socket is not sending a new line with each log message the Logstash server (1.1.12) interpret it as incomplete. This results in all logs sent being interpreted as a single entry when the socket closes.

Fixed by adding a new line to the end of the message to ensure that the logstash server interprets as a complete log message.

I've updated the tests to reflect this. It might be that previous versions of Logstash server do not have this requirement.

…sh server interprets as a complete log message.
jaakkos added a commit that referenced this pull request May 23, 2013
Logs sent to logstash are interpreted as stream and therefore are incorrectly parsed
@jaakkos jaakkos merged commit eb9dd33 into jaakkos:master May 23, 2013
@jaakkos
Copy link
Owner

jaakkos commented May 23, 2013

Thanks!

@gwhitelaw gwhitelaw deleted the add_new_line_to_flush_socket branch June 6, 2013 12:38
br0p0p added a commit to br0p0p/winston-logstash that referenced this pull request Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants