Add docs for resource out otel

[cb645j]

Summary by CodeRabbit

• New Features

  • Added a configuration option to the OpenTelemetry output plugin to map a Resource attribute key for log messages (configurable, default: none), available in Fluent Bit and YAML configurations.

• Documentation

  • Updated OpenTelemetry output plugin docs and examples to show the new configuration and how to map message resource attributes.

[coderabbitai]

Warning

Review limit reached

@eschabell, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 12 minutes and 56 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ac4a9ba9-bba6-4f4e-b7b6-4de3fe233130

📥 Commits

Reviewing files that changed from the base of the PR and between 8294566 and 96c6a6b.

📒 Files selected for processing (1)

• pipeline/outputs/opentelemetry.md

📝 Walkthrough

Walkthrough

A new configuration option logs_resource_attributes_message_key is added to the OpenTelemetry output plugin documentation (default _none_). The parameter table and Fluent Bit examples (YAML and fluent-bit.conf) were updated to include mappings for message resource attributes like application_id and service_name.

Changes

OpenTelemetry Output Configuration

Layer / File(s)	Summary
Add parameter and update examples pipeline/outputs/opentelemetry.md	Added new configuration option logs_resource_attributes_message_key (string, default: _none_) to the plugin parameter table and inserted corresponding entries in the Fluent Bit YAML and fluent-bit.conf examples (application_id, service_name).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

5.0

Suggested reviewers

• cosmo0920

Poem

🐰 A tiny key hops into place,
in docs it finds a tidy space,
logs_resource_attributes_message_key — so neat,
maps service and app to make logs complete,
a rabbit's cheer for telemetry grace!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Add docs for resource out otel' uses abbreviated/unclear terms ('out', 'otel') that obscure the actual change, making it difficult to understand the specific documentation update without context.	Consider clarifying the title to be more explicit, such as 'Add documentation for OpenTelemetry output plugin resource attributes' to make the change immediately understandable to reviewers.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pipeline/outputs/opentelemetry.md`:
- 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.”
- Line 139: The fluent-bit.conf example includes a new option that is missing
from the fluent-bit.yaml example; update the YAML example in
pipeline/outputs/opentelemetry.md (the fluent-bit.yaml code block around the
current examples) to include the equivalent key/value entry so both examples
demonstrate the same feature set—locate the fluent-bit.conf block to see the
exact option name and value, then add the matching YAML mapping/key under the
fluent-bit.yaml section with the same semantic setting and a brief inline
comment mirroring the conf example.
- Around line 189-190: Remove the invalid Fluent Bit OpenTelemetry output option
`logs_resource_attributes_message_key` and instead demonstrate configuring
resource attributes via a processors pipeline using the `opentelemetry_envelope`
processor with `content_modifier`; specifically, delete the two lines containing
`logs_resource_attributes_message_key application_id` and
`logs_resource_attributes_message_key service_name` and replace (or document)
using an `opentelemetry_envelope` processor block with `content_modifier` rules
to add/rename resource attributes for logs as per the OpenTelemetry processor
usage.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dc38f3c and d51e2fd.

📒 Files selected for processing (1)

• pipeline/outputs/opentelemetry.md

[eschabell]

@cb645j a few ai review issues to be solved please, see above comment.

[eschabell]

@cb645j thanks for the updates, but it's now raised conflicts that I need you to resolve before I can review?

[eschabell]

@cb645j resolved the conflict, can you verify that your updates are intact?

[eschabell]

@cb645j cleaned up the conflict, can. you verify everything is intact you wanted to submit and address the changes listed below? Thanks for your patience and effort here!

[eschabell]

@cb645j cleaned up all the issues with PR.

[eschabell]

@cb645j waiting on code PR merging.