Skip to content
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

Add no-piggyback-errors flag to syslog-parser() and syslog related source drivers. #5063

Merged

Conversation

kovgeri01
Copy link
Collaborator

Backport of #245 by @bazsi

Just like rfc3164, make it possible to report rfc5424 style parsing issues
as tags.

Signed-off-by: Balazs Scheidler <[email protected]>
This tells syslog-ng not to wipe out the input message in syslog-parser() and
source encapsulated syslog parsers when there's a parse issue.

For example:

    parser { syslog-parser(flags(syslog-protocol, no-piggyback-errors)); };

With that in place, $MSG retains its original value and various tags (e.g.
the syslog.* ones) report what kind of issues we detected with the messsage.

When the message is sent to a syslog-like destination, we will prepend
a header.

Basically this makes 5424 and 3164 parsing more similar. Previously 5424 parsing
reported its errors by completely wiping out the the existing log message
fields and adding a message attributed to "syslog-ng" itself. But this
message was coming from the same source and not internal().




Signed-off-by: Balazs Scheidler <[email protected]>
news/feature-5063.md Outdated Show resolved Hide resolved
Signed-off-by: Kovacs, Gergo Ferenc <[email protected]>
@kovgeri01 kovgeri01 force-pushed the retain-rawmsg-on-msg-parse-errors branch from 81d9719 to 72bffce Compare August 23, 2024 14:07
@kovgeri01 kovgeri01 requested a review from HofiOne August 23, 2024 14:07
@kovgeri01 kovgeri01 merged commit 8ecfed4 into syslog-ng:master Aug 23, 2024
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants