Skip to content

Conversation

@kovgeri01
Copy link
Contributor

Backport of #245 by @bazsi

bazsi added 5 commits August 13, 2024 13:59
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]>
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
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