-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
logstash multiline filter: last part of message flush #1938
Comments
It works by setting enable_flush to true in the multiline filter. |
This is fixed in master and scheduled for the 1.5.0 release. |
enable_flush is going away and was intented only for testing the plugin, not for production. This setting will be removed in the next release. |
OK.Thanks for the update. |
While using enable_flush it works fine. But when using the grok match filter after the flush of events, the tag values gets duplicated. Is there any fix for it ? |
I'm trying out 1.5.0RC2, but I'm not seeing any change when the terminal event is a multiline event. I've distilled the example into a gist. Edit: Nevermind. I realized that moving from the multiline codec to the multiline filter was required. |
Dear Logstash Team, |
@harveysun, as others mentioned, you can use the multiline filter (not multiline codec): |
There was a know issue in the multiline filter that it doesn't print the last part of the input being filtered as it is still waiting for a pattern to follow and it isn't flushed out.
Has the issue been resolved. If so how?Is there a tag to flush out the last part?
The text was updated successfully, but these errors were encountered: