Skip to content

Add docs for resource out otel #2405

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

Open
cb645j wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Add docs for resource out otel #2405

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d51e2fd
Add docs for resource out otel
Mar 2, 2026
8294566
Merge branch 'master' into feature/opentelemetry_out_docs_resource
eschabell May 15, 2026
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
17 changes: 11 additions & 6 deletions pipeline/outputs/opentelemetry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,9 @@ Only HTTP endpoints are supported.
| `logs_max_scopes` | Set the maximum number of OTLP log scopes per resource (`0` disables the limit). | `0` |
| `logs_metadata_key` | Set the key to look up in the metadata. | `otlp` |
| `logs_observed_timestamp_metadata_key` | Specify an `ObservedTimestamp` key. | `$ObservedTimestamp` |
| `logs_resource_metadata_key` | Specify a `Resource` key. | `Resource` |
| `logs_resource_metadata_key` | Specify a `Resource` key. | `Resource`
| `logs_resource_attributes_message_key` | Specify a `Resource` key. | _none_ |
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Mar 2, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Clarify the new key’s purpose in the parameter table.

At Line 41, the description currently matches logs_resource_metadata_key semantics and is too vague. Please make it explicit that this is a message-field key promoted into Resource attributes.

Suggested doc wording 
-| `logs_resource_attributes_message_key`    | Specify a `Resource` key.                                                      | _none_                                                                      |
+| `logs_resource_attributes_message_key`    | Specify a message key whose value is added as a `Resource` attribute.          | _none_                                                                      |
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| `logs_resource_attributes_message_key` | Specify a `Resource` key. | _none_ |
| `logs_resource_attributes_message_key` | Specify a message key whose value is added as a `Resource` attribute. | _none_ |
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@pipeline/outputs/opentelemetry.md` at line 41, Update the param table row for
logs_resource_attributes_message_key so its description clearly states that this
key names a message-field whose value will be promoted into the OpenTelemetry
Resource attributes (distinct from logs_resource_metadata_key which maps
metadata fields); replace the vague text with an explicit phrase like “Specify
the message field key whose value will be promoted into the Resource
attributes.”

Copy link
Copy Markdown
Collaborator

@eschabell eschabell Mar 3, 2026

Choose a reason for hiding this comment

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

@cb645j add a bit more clarity for each one in the description please.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Mar 3, 2026

Choose a reason for hiding this comment

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

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

Copy link
Copy Markdown
Collaborator

@eschabell eschabell May 15, 2026

Choose a reason for hiding this comment

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

@cb645j resolved the conflict, can you address this issue?

| `log_response_payload` | Specify if the response payload should be logged or not. | `true` |
| `logs_severity_number_message_key` | Specify a `SeverityNumber` key. | `$severityNumber` |
| `logs_severity_number_metadata_key` | Specify a `SeverityNumber` key. | `$SeverityNumber` |
| `logs_severity_text_message_key` | Specify a `SeverityText` key. | `$SeverityText` |
Expand Down Expand Up @@ -156,6 +158,7 @@ pipeline:
logs_trace_id_message_key: trace_id
logs_severity_text_message_key: loglevel
logs_severity_number_message_key: lognum

Comment thread
coderabbitai[bot] marked this conversation as resolved.
# add user-defined labels
add_label:
- app fluent-bit
Expand Down Expand Up @@ -200,11 +203,13 @@ pipeline:
Log_response_payload True
Tls On
Tls.verify Off
Logs_Body_Key $message
Logs_Span_Id_Message_Key span_id
Logs_Trace_Id_Message_Key trace_id
Logs_Severity_Text_Message_Key loglevel
Logs_Severity_Number_Message_Key lognum
Logs_Body_Key $message
Logs_Span_Id_Message_Key span_id
Logs_Trace_Id_Message_Key trace_id
Logs_Severity_Text_Message_Key loglevel
Logs_Severity_Number_Message_Key lognum
Logs_Resource_Attributes_Message_Key application_id
Logs_Resource_Attributes_Message_Key service_name
# add user-defined labels
Add_Label app fluent-bit
Add_Label color blue
Expand Down
Loading