4.6 destination flags #54
Conversation
And placeholders for other undocumented destination flags
|
|
||
| - `ignore-errors`: <!-- FIXME --> |
There was a problem hiding this comment.
The ignore-error flag silently drops messages which have not been successfully sent out because of unrecoverable low-level errors (e.g. I/O errors).
|
|
||
| - `ignore-errors`: <!-- FIXME --> | ||
| - `no-multi-line`: The `no-multi-line` flag disables line-breaking in the messages: the entire message is converted to a single line. | ||
| - `no-seqnum-all`: <!-- FIXME --> |
There was a problem hiding this comment.
The no-seqnum-all flag explicitly disables new seqnum generation for forwarded messages, which is the default behavior.
@bazsi Do I understand this right? I feel like this should return 0 seqnum even for locally generated messages, but the flag does not clear the LWO_SEQNUM field:
https://github.com/syslog-ng/syslog-ng/blob/1f0a854d0227dd95410fbc094997d8b0b225cd41/lib/logwriter.c#L2037
Do we even need this flag? The no-seqnum flag (not yet released) does the full disabling, that I have mentioned. I think it is confusing to have both.
Also, why do we need the seqnum flag, which sets the default behavior?
I feel like there are 3 cases:
- local messages get a generated seqnum, forwarded messages keep their own.
- all messages get a generated seqnum.
- neither local, nor forwarded messages get a seqnum (SEQNUM = 0).
The first is the default behavior, which does not necessarily need an explicit flag.
The second is enabled by seqnum-all.
The third is enabled by no-seqnum.
I don't see the point of having any other SEQNUM related flags.
| - *no-multi-line*: The `no-multi-line` flag disables line-breaking in the messages: the entire message is converted to a single line. | ||
| - *syslog-protocol*: The `syslog-protocol` flag instructs the driver to format the messages according to the new IETF syslog protocol standard (RFC5424), but without the frame header. If this flag is enabled, macros used for the message have effect only for the text of the message, the message header is formatted to the new standard. Note that this flag is not needed for the `syslog` driver, and that the `syslog` driver automatically adds the frame header to the messages. | ||
| - `syslog-protocol`: The `syslog-protocol` flag instructs the driver to format the messages according to the new IETF syslog protocol standard (RFC5424), but without the frame header. If this flag is enabled, macros used for the message have effect only for the text of the message, the message header is formatted to the new standard. Note that this flag is not needed for the `syslog` driver, and that the `syslog` driver automatically adds the frame header to the messages. | ||
| - `threaded`: <!-- FIXME --> |
There was a problem hiding this comment.
The threaded flag enables multithreading for the current destination, even if the global threaded(no) option is set. For more information about multithreading, see: https://axoflow.com/docs/axosyslog-core/chapter-multithreading/configuring-multithreading/#example-enabling-multithreading
No description provided.