-
Notifications
You must be signed in to change notification settings - Fork 47.1k
fix(core): Set rfc3164 option to false for syslog client initialization #20664
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
base: master
Are you sure you want to change the base?
fix(core): Set rfc3164 option to false for syslog client initialization #20664
Conversation
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.
No issues found across 1 file
…reaming-and-vector-as-a
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
...es/cli/src/eventbus/message-event-bus-destination/message-event-bus-destination-syslog.ee.ts
Show resolved
Hide resolved
…reaming-and-vector-as-a
…reaming-and-vector-as-a
E2E Tests: n8n tests passed after 3m 20.7s Run Details
Groups
This message was posted automatically by
currents.dev | Integration Settings
|
E2E Tests: n8n tests passed after 3m 48.5s Run Details
Groups
This message was posted automatically by
currents.dev | Integration Settings
|
…reaming-and-vector-as-a
…reaming-and-vector-as-a
…reaming-and-vector-as-a
…reaming-and-vector-as-a
Summary
n8n's syslog destination defaults to RFC 3164 format, causing Vector and modern syslog servers to incorrectly parse JSON messages - the beginning of the JSON payload gets truncated into the appname field instead of appearing in the message body
Related Linear tickets, Github issues, and Community forum posts
PAY-3962
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)