LOG-8090: escape 'new line' (\n) in EventRouter message

[vparfonov]

Description

This PR addresses a issue where Syslog output format corruption occurs if log messages generated by the Eventrouter contain newline characters (\n), this leads to malformed syslog data.
This fix ensures that the log message payload is properly escaped, preventing the introduction of malformed lines.

When JSON contains \n that becomes a real newline after decoding; sending real newlines in syslog breaks framing and creates split events. This change escapes newline characters (\n) in message payloads so the syslog sink emits a single safe line.

/cc @cahartma @kattz-kawa
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://issues.redhat.com/browse/LOG-8090
• Enhancement proposal:

[openshift-ci-robot]

@vparfonov: This pull request references LOG-8090 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set.

Details

In response to this:

Description

This PR addresses a issue where Syslog output format corruption occurs if log messages generated by the Eventrouter contain newline characters (\n), this leads to malformed syslog data.
This fix ensures that the log message payload is properly escaped, preventing the introduction of malformed lines.

/cc @cahartma @kattz-kawa
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://issues.redhat.com/browse/LOG-8090
• Enhancement proposal:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[vparfonov]

/hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vparfonov
Once this PR has been reviewed and has the lgtm label, please assign xperimental for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vparfonov]

/test functional-target

[vparfonov]

/test e2e-target

[openshift-ci]

@vparfonov: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@vparfonov: This pull request references LOG-8090 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set.

Details

In response to this:

Description

This PR addresses a issue where Syslog output format corruption occurs if log messages generated by the Eventrouter contain newline characters (\n), this leads to malformed syslog data.
This fix ensures that the log message payload is properly escaped, preventing the introduction of malformed lines.

When JSON contains \n that becomes a real newline after decoding; sending real newlines in syslog breaks framing and creates split events. This change escapes newline characters (\n) in message payloads so the syslog sink emits a single safe line.

/cc @cahartma @kattz-kawa
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://issues.redhat.com/browse/LOG-8090
• Enhancement proposal:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[vparfonov]

/hold cancel