Skip to content

no-piggyback-errors #145

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.

Sign up for GitHub

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

Merged
zsoltgyulai94 merged 5 commits into from
Jun 10, 2025
Merged

no-piggyback-errors #145

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
17cc1fb
Added "no-piggyback-errors" to parser flags.
zsoltgyulai94 Oct 2, 2024
cbe17fe
Fixed description of parser options.
zsoltgyulai94 Oct 3, 2024
f2b5765
Fixed syslog-error, to syslog:error, and referenced a section detailing
zsoltgyulai94 Oct 17, 2024
a725715
Added piggyback-errors.
zsoltgyulai94 Jun 10, 2025
4310e7d
Merge branch 'master' into doc-parser-no-PB
zsoltgyulai94 Jun 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion _includes/doc/admin-guide/options/source-flags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
## flags()

|Type:| assume-utf8, empty-lines, expect-hostname, kernel, no-hostname, no-multi-line, no-parse, sanitize-utf8, store-legacy-msghdr, store-raw-message, syslog-protocol, threaded, validate-utf8|
|Accepted values:| assume-utf8, empty-lines, expect-hostname, kernel, no-hostname, no-multi-line, no-parse, sanitize-utf8, store-legacy-msghdr, store-raw-message, syslog-protocol, threaded, validate-utf8, no-piggyback-errors|
|Default: | empty set|

*Description:* Specifies the log parsing options of the source.
Expand Down Expand Up @@ -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.
- *piggyback-errors*: On failure, the old behaviour is used (clearing the entire message then syslog-ng will generate a new message in place of the old one describing the parser's error).
[^1]: The byte order mark (BOM) is a Unicode character used to signal the byte-order of the message text.