-
Notifications
You must be signed in to change notification settings - Fork 6
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
base: master
Are you sure you want to change the base?
no-piggyback-errors #145
Conversation
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. |
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.
This description does not make much sense to me.
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.
@zsoltgyulai94 could you please check this PR description and rephrase based on it, TIA!
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.
Yeah, sorry, wasn't aware of that PR. Fixed.
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. |
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.
it is syslog:error not syslog-error.
the tags the parser can add to the message could also be referenced
tags. Signed-off-by: Zsolt Gyulai (zgyulai) <[email protected]>
Added "no-piggyback-errors" to parser flags.
Signed-off-by: Zsolt Gyulai (zgyulai) [email protected]