open-telemetry / open-telemetry/opentelemetry-python-contrib
Audit all packages to ensure NoOpTracerProvider works
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
An issue was found in the wsgi instrumentation by integration tests in the core repository. The issue should have been caught by unit tests in the instrumentation using the NoOpTracerProvider.
The outcome of this issue is to ensure each instrumentation contains a test using the NoOpTracerProvider and that it does not rely on the OpenTelemetry SDK:
- #994
- #993
- #992
- #991
- #990
- #989
- #988
- #987
- #986
- #985
- #984
- #983
- #982
- #981
- #980
- #979
- #978
- #977
- #976
- #975
- #974
- #973
- #972
- #971
- #970
- #969
- #968
- #967
- #966
- #965
- #964
- #963
- #962
- #961
- #960
- #959
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the WSGI instrumentation issue and its unit tests, then review the unchecked package issues listed in the checklist. Each instrumentation should have a test using NoOpTracerProvider and should not rely on the OpenTelemetry SDK; run the relevant unit tests to verify the audit is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100