open-telemetry / open-telemetry/opentelemetry-python-contrib

Instrumentations do not use `tracer_provider` argument to create a tracer instances

Open
#401 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue help wanted triaged
Dominant language
Python
Stars
1.1k
Forks
1.1k
Avg merge
4d 15h
Merged PRs (30d)
16

Description

Users can optionally pass an instance of TracerProvider to SomeInstrumentator.instrument(tracer_provider=...). Instrumentations should use this tracer_provider and fall back to global tracer provider if not given. As of now some instrumentations directly use global tracer provider which is not expected because providers can have different configuration such as Resource.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the instrumentation implementations that create tracers and identify the ones using the global tracer provider instead of the instrument method's tracer_provider argument. Verify that an explicitly supplied provider is used and that the global provider remains the fallback, including coverage for providers with different Resource configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.