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

no-piggyback-errors #145

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

zsoltgyulai94
Copy link
Contributor

Added "no-piggyback-errors" to parser flags.

Signed-off-by: Zsolt Gyulai (zgyulai) [email protected]

Signed-off-by: Zsolt Gyulai (zgyulai) <[email protected]>
@@ -139,5 +139,6 @@
If the BOM[^1] character is missing, but the message is otherwise UTF-8
compliant, {{ site.product.short_name }} automatically adds the BOM character to the
message.
- *no-piggyback-errors*: This option configures syslog-ng OSE to ignore parsing errors caused by piggybacked messages. If the parser encounters issues separating multiple messages sent together, it skips them without raising an error.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This description does not make much sense to me.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zsoltgyulai94 could you please check this PR description and rephrase based on it, TIA!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, sorry, wasn't aware of that PR. Fixed.

@HofiOne HofiOne requested a review from bazsi October 3, 2024 06:59
Signed-off-by: Zsolt Gyulai (zgyulai) <[email protected]>
@@ -139,5 +139,7 @@
If the BOM[^1] character is missing, but the message is otherwise UTF-8
compliant, {{ site.product.short_name }} automatically adds the BOM character to the
message.
- *no-piggyback-errors*: On failure, the original message will be left as it was before parsing, the value of `$MSGFORMAT` will be set to `syslog-error`, and a tag will be placed on the message corresponding to the parser's failure.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is syslog:error not syslog-error.

the tags the parser can add to the message could also be referenced

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.

Add no-piggyback-errors flag to syslog-parser() and syslog related source drivers
3 participants