-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat(inputs.socket_ listener): Allow to specify message separator for streams #12187
feat(inputs.socket_ listener): Allow to specify message separator for streams #12187
Conversation
Co-authored-by: reimda <reimda@users.noreply.github.com>
Co-authored-by: reimda <reimda@users.noreply.github.com>
5531538
to
631c0c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one change @srebhan then I'm +1
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
resolves #6025
potentially resolves #6920
partially resolves ##11952
This PR adds the ability to specify how messages should be split for stream sockets (e.g. TCP) using the new
splitting_strategy
option. Currently the PR implements splitting bynewline
(current behavior, default), bynull
byte, by a user specified byte-sequence (delimiter
), by fixed message length or by dynamic message length found in some message header "field".