From 0142b7c38c4444a3484c5e94ec134519a61c1ba0 Mon Sep 17 00:00:00 2001 From: PraveenJeffriAndroidDeveloper Date: Tue, 2 Sep 2025 09:39:40 +0530 Subject: [PATCH] docs: add logs_body_key_attributes option for opentelemetry output Signed-off-by: PraveenJeffriAndroidDeveloper --- pipeline/outputs/opentelemetry.md | 1 + 1 file changed, 1 insertion(+) diff --git a/pipeline/outputs/opentelemetry.md b/pipeline/outputs/opentelemetry.md index 0068eb23a..fb97cd193 100644 --- a/pipeline/outputs/opentelemetry.md +++ b/pipeline/outputs/opentelemetry.md @@ -37,6 +37,7 @@ Only HTTP endpoints are supported. | `logs_span_id_metadata_key` | Specify a `SpanId` key` to look up in the metadata. | `$SpanId` | | `logs_trace_id_metadata_key` | Specify a `TraceId` key to look up in the metadata. | `$TraceId` | | `logs_attributes_metadata_key` | Specify an `Attributes` key to look up in the metadata. | `$Attributes` | +| `logs_body_key_attributes` | When enabled (`true`), Fluent Bit will place all parsed JSON fields (except the one mapped by `logs_body_key`) inside the `attributes` section of the OpenTelemetry `LogRecord`. This is useful if you want structured key/value pairs as attributes, while still mapping a specific field (defined by `logs_body_key`) to the `body`. | `false` | | `workers` | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. | `0` | ## Get started