Skip to content

docs: add instrumentation naming convention to contributing guide#4754

Open
krrishapatel wants to merge 1 commit into
open-telemetry:mainfrom
krrishapatel:docs/instrumentation-naming-convention
Open

docs: add instrumentation naming convention to contributing guide#4754
krrishapatel wants to merge 1 commit into
open-telemetry:mainfrom
krrishapatel:docs/instrumentation-naming-convention

Conversation

@krrishapatel

Copy link
Copy Markdown

Description

Adds a note to the instrumentation guidelines section of CONTRIBUTING.md documenting that instrumentations should use their top-level package name (e.g. "opentelemetry.instrumentation.requests") as a fixed string when obtaining a tracer or meter, rather than __name__.

Fixes #910

Type of change

  • This change requires a documentation update

How Has This Been Tested?

Documentation-only change.

Does This PR Require a Core Repo Change?

  • No.

Assisted-by: Claude Opus 4.6

@krrishapatel krrishapatel requested a review from a team as a code owner June 28, 2026 02:56

@xrmx xrmx 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.

This contains unrelated changes

@github-project-automation github-project-automation Bot moved this to Reviewed PRs that need fixes in Python PR digest Jul 2, 2026
Add a note under the instrumentation guidelines that tracers and meters
should be obtained using the top-level instrumentation package name as a
fixed string (e.g. "opentelemetry.instrumentation.requests") rather than
__name__, which varies by submodule.

Assisted-by: Claude Opus 4.6
@krrishapatel krrishapatel force-pushed the docs/instrumentation-naming-convention branch from 65484c8 to dd792c1 Compare July 2, 2026 19:38
@krrishapatel

Copy link
Copy Markdown
Author

Thanks @xrmx — you're right, the logging README change was unrelated. I've rebased to remove it; this PR now only touches CONTRIBUTING.md with the instrumentation naming convention guidance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Reviewed PRs that need fixes

Development

Successfully merging this pull request may close these issues.

Add note to contributing guide about instrumentation name

2 participants