open-telemetry / open-telemetry/opentelemetry-python-contrib
Implement migration plan for selected instrumentations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
A followup of https://github.com/open-telemetry/opentelemetry-python-contrib/issues/2351
Tracking issue to track progress of semantic convention stability migration for the below instrumentations.
Finished:
opentelemetry-instrumentation-requests https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2002
opentelemetry-instrumentation-wsgi https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2425
opentelemetry-instrumentation-flask https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2454
opentelemetry-instrumentation-asgi https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2610
opentelemetry-instrumentation-httpx https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2631
opentelemetry-instrumentation-fastapi https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2682
opentelemetry-instrumentation-aiohttp-client https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2675
opentelemetry-instrumentation-django #2714
opentelemetry-instrumentation-urllib3 #2681
opentelemetry-instrumentation-urllib #2680
opentelemetry-instrumentation-falcon #2680
opentelemetry-instrumentation-dbapi #2929
opentelemetry-instrumentation-sqlalchemy #2679
opentelemetry-instrumentation-redis #2930
opentelemetry-instrumentation-mysql #2931
opentelemetry-instrumentation-mysqlclient #2932
opentelemetry-instrumentation-psycopg #2928
opentelemetry-instrumentation-psycopg2 #2678
opentelemetry-instrumentation-pymysql #2933
opentelemetry-instrumentation-sqlite3 #2934
WIP:
Remaining:
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
Review follow-up issue #2351 and the listed instrumentation packages and pull requests. The issue has no remaining or WIP items, so confirm whether any migration work is still open before starting; completion criteria are not defined here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, fastapi, flask, mysql, python, redis, sqlalchemy, sqlite
- Domain
- backend, observability
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100