rsyslog: multi-line message support #180
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RyanSkraba
previously approved these changes
Dec 4, 2025
Contributor
Author
|
The CI workflow failed to |
In newer version of google-re2 dependency, building wheel fails with message: ``` ERROR: The 'build' command is only supported from within a workspace (below a directory having a MODULE.bazel file). ```
Retry to send when the SSL connection was closed unexpectedly with message 'EOF occurred in violation of protocol'.
Syslog over TCP (RFC 6587) supports 2 message framing methods:
- Octet-counted framing: Each message is prefixed with its
length and a space (<length> <message>).
- Non-transparent framing: Each message is terminated by a
newline (\n).
So far, non-transparent framing was used by journalpump,
and multi-line log messages were truncated to 1st line.
We keep this behavior by default, but now expose a new config
allowing to switch to octet-counted framing, so that
multi-line log messages only get truncated by max size.
jclarysse
force-pushed
the
jclarysse/feat-rsyslog-sender-multiline-support
branch
from
f6fc322 to
f1f03c7
Compare
RyanSkraba
approved these changes
Dec 5, 2025
This was referenced Dec 9, 2025
jclarysse
added a commit
to jclarysse/journalpump
that referenced
this pull request
Dec 15, 2025
The recently added config `truncate_multiline`(PR Aiven-Open#180 and Aiven-Open#181) might raise wrong user expectation as it relies on a workaround that is not supported by all syslog servers. I propose to keep this dev but rename the config to `octet_counted_framing` which is what it actually does, and inverse the value. This should avoid confusion and prevent any future misuse.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why change
Journalpump sends Syslog messages over TCP using non-transparent-framing. As a result, multi-line messages are truncated to the 1st line.
Solution proposal
This PR keeps the default behavior but now exposes a new Journalpump config
truncate_multiline. When set tofalse, Journalpump sends Syslog messages over TCP using octet-counting and log messages only get truncated by max size. This is especially helpful when collecting Kafka server logs containing start configs and error stack traces.Additional information
The PR also includes a minor improvement:
EOF occurred in violation of protocol (_ssl.c:2427).Aiven internal: FLEET-6148