Audit all packages to ensure NoOpTracerProvider works

[codeboten]

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:

• Audit and test opentelemetry-instrumentation-aiohttp-client #994
• Audit and test opentelemetry-instrumentation-aiopg #993
• Audit and test opentelemetry-instrumentation-asgi #992
• Audit and test opentelemetry-instrumentation-asyncpg #991
• Audit and test opentelemetry-instrumentation-aws-lambda #990
• Audit and test opentelemetry-instrumentation-boto #989
• Audit and test opentelemetry-instrumentation-botocore #988
• Audit and test opentelemetry-instrumentation-celery #987
• Audit and test opentelemetry-instrumentation-dbapi #986
• Audit and test opentelemetry-instrumentation-django #985
• Audit and test opentelemetry-instrumentation-elasticsearch #984
• Audit and test opentelemetry-instrumentation-falcon #983
• Audit and test opentelemetry-instrumentation-fastapi #982
• Audit and test opentelemetry-instrumentation-flask #981
• Audit and test opentelemetry-instrumentation-grpc #980
• Audit and test opentelemetry-instrumentation-httpx #979
• Audit and test opentelemetry-instrumentation-jinja2 #978
• Audit and test opentelemetry-instrumentation-kafka-python #977
• Audit and test opentelemetry-instrumentation-logging #976
• Audit and test opentelemetry-instrumentation-mysql #975
• Audit and test opentelemetry-instrumentation-pika #974
• Audit and test opentelemetry-instrumentation-psycopg2 #973
• Audit and test opentelemetry-instrumentation-pymemcache #972
• Audit and test opentelemetry-instrumentation-pymongo #971
• Audit and test opentelemetry-instrumentation-pymysql #970
• Audit and test opentelemetry-instrumentation-pyramid #969
• Audit and test opentelemetry-instrumentation-redis #968
• Audit and test opentelemetry-instrumentation-requests #967
• Audit and test opentelemetry-instrumentation-sklearn #966
• Audit and test opentelemetry-instrumentation-sqlalchemy #965
• Audit and test opentelemetry-instrumentation-sqlite3 #964
• Audit and test opentelemetry-instrumentation-starlette #963
• Audit and test opentelemetry-instrumentation-tornado #962
• Audit and test opentelemetry-instrumentation-urllib #961
• Audit and test opentelemetry-instrumentation-urllib3 #960
• Audit and test opentelemetry-instrumentation-wsgi #959

[lzchen]

Discussed in 3/17 SIG:

Perhaps we can modify testbaseutils for loading only an api so instrumentations can test only against the api classes

[ocelotl]

testbaseutils for loading only an api so instrument

Sorry, can you provide more context, please?

[srikanthccv]

testbaseutils for loading only an api so instrument

Sorry, can you provide more context, please?

All the instrumentation tests inherit this TestBase. One thing we could do is to not set up provider here and see if tests produce any error in the absence of sdk tracer provider.

[ocelotl]

testbaseutils for loading only an api so instrument

Sorry, can you provide more context, please?

All the instrumentation tests inherit this TestBase. One thing we could do is to not set up provider here and see if tests produce any error in the absence of sdk tracer provider.

Got it, thanks ✌️

[zhihali]

I have checked and found the Celery and Starlette is merged and could be marked finished.