docs: add logs_body_key_attributes option for opentelemetry output #2055
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: PraveenJeffriAndroidDeveloper <praveenjeffri@gmail.com>
PraveenJeffriAndroidDeveloper
force-pushed
the
add-logs-body-key-attributes-doc
branch
from
008f382 to
0142b7c
Compare
esmerel
approved these changes
Sep 2, 2025
| | `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` | |
There was a problem hiding this comment.
Suggested change
| | `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` | | |
| | `logs_body_key_attributes` | When enabled (`true`), Fluent Bit places all parsed JSON fields (except the one mapped by `logs_body_key`) inside the `attributes` section of the OpenTelemetry `LogRecord`. Use to create structured key/value pairs as attributes, while still mapping a specific field (defined by `logs_body_key`) to the `body`. | `false` | |
Just trying to make it a little more active and avoid "useful". Looks good to me though!
@fluent/fluent-bit-maintainers should review for technical accuracy.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR documents the logs_body_key_attributes option for the OpenTelemetry output plugin.
It allows placing the JSON body content inside attributes of the OTEL LogRecord.
This feature is mentioned in issues (fluent/fluent-bit#10445), but not in the docs.