Skip to content
Merged
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions content/docs/configuration/crds/v1beta1/fluentbit_types.md
Original file line number Diff line number Diff line change
Expand Up @@ -1143,6 +1143,14 @@ ForwardOptions defines custom forward output plugin options, see https://docs.fl
### Require_ack_response (bool, optional) {#forwardoptions-require_ack_response}


### Retain_Metadata_In_Forward_Mode (bool, optional) {#forwardoptions-retain_metadata_in_forward_mode}
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added Retain_Metadata_In_Forward_Mode field documentation based on the new field added in pkg/sdk/logging/api/v1beta1/fluentbit_types.go. The field controls fluent-bit metadata forwarding and defaults to false for fluentd compatibility.

Source: kube-logging/logging-operator#2227


Controls whether fluent-bit appends log event metadata when forwarding records. Available since fluent-bit 5.0.4; defaults to `true` in fluent-bit 5.0.5 and later.

Fluentd does not understand the fluent-bit metadata format and drops these records as "invalid event". To maintain compatibility with fluentd, the operator defaults this to `false` for Forward mode targets.

Set to `true` only when forwarding between fluent-bit instances.

### Retry_Limit (string, optional) {#forwardoptions-retry_limit}


Expand Down
Loading