Skip to content

Add log_bridge.name and log_bridge.version Instrumentation Scope attributes#3716

Draft
cijothomas wants to merge 4 commits into
open-telemetry:mainfrom
cijothomas:cijothomas/log-bridge-attrs
Draft

Add log_bridge.name and log_bridge.version Instrumentation Scope attributes#3716
cijothomas wants to merge 4 commits into
open-telemetry:mainfrom
cijothomas:cijothomas/log-bridge-attrs

Conversation

@cijothomas

Copy link
Copy Markdown
Member

Draft for #1550, following Proposal A. Adds log_bridge.name and log_bridge.version as opt-in Instrumentation Scope attributes (Development stability) to identify the log bridge, distinct from the producer reported as the scope name.

@thompson-tomo thompson-tomo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What about having these attributes under the otel.* namespace?

Alternatively what about using the otel.component.* attributes with a new type?

Third option, what about log.bridge.* that way it would sit alongside log.file attributes etc?

@cijothomas

Copy link
Copy Markdown
Member Author

Thanks @thompson-tomo. +1 to option 3 — log.bridge.* is the right home for two reasons:

  1. It sits alongside the existing log.file.* / log.iostream / log.record.*, so bridge authors will actually find it.
  2. The naming guideline in docs/general/naming.md explicitly prefers the dotted {object}.{property} form and says to avoid underscores between namespace segments ({object}_{property}). Since log is already an established top-level namespace, log.bridge.name / log.bridge.version is the conventional spelling — log_bridge.* introduces a new top-level namespace with an underscore in it, which is atypical for the repo.

I'll update the PR to rename log_bridge.*log.bridge.*.

Comment thread .chloggen/log-bridge-attributes.yaml Outdated
Comment thread .chloggen/log-bridge-attributes.yaml Outdated
@github-actions

Copy link
Copy Markdown

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.

@github-actions github-actions Bot added the Stale label May 29, 2026
@github-actions github-actions Bot closed this Jun 5, 2026
@cijothomas

Copy link
Copy Markdown
Member Author

Reopening, not stale.

@thompson-tomo

Copy link
Copy Markdown
Contributor

@cijothomas did u forget to reopen this pr?

@pellared pellared reopened this Jun 10, 2026
@pellared pellared removed the Stale label Jun 10, 2026
@pellared

Copy link
Copy Markdown
Member

Reopened. I guess that @cijothomas lacks permission to reopen.

@cijothomas cijothomas force-pushed the cijothomas/log-bridge-attrs branch from 887295b to 8bf3777 Compare June 11, 2026 05:51
@github-actions github-actions Bot added the enhancement New feature or request label Jun 11, 2026
@github-actions

Copy link
Copy Markdown

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.

@github-actions github-actions Bot added the Stale label Jun 26, 2026
@pellared pellared removed the Stale label Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:log enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants