What problem do you want to solve?
Most instrumentation libraries in this project supports explicitly passing a TracingProvider object when instrumenting a third party library. This is critical for testing purposes because if not passes, then a global TracingProvider is used and that one can only be set once within a python process, meaning once for all the tests you run. It would/should be possible to also provide this in the aiohttp server instrumentation library.
Describe the solution you'd like
The solution I would like to see (following the style of the other instrumentation libraries within this project) is that the tracer used here should come from a TracerProvider if one is passed upon instrumentation.
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
None
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
What problem do you want to solve?
Most instrumentation libraries in this project supports explicitly passing a
TracingProviderobject when instrumenting a third party library. This is critical for testing purposes because if not passes, then a globalTracingProvideris used and that one can only be set once within a python process, meaning once for all the tests you run. It would/should be possible to also provide this in the aiohttp server instrumentation library.Describe the solution you'd like
The solution I would like to see (following the style of the other instrumentation libraries within this project) is that the
tracerused here should come from aTracerProviderif one is passed upon instrumentation.Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
None
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.