GA OpenTelemetry tracing plugin

[lmolkova]

We have a partner ask to GA OTel tracing plugins across all languages in [Zn], this is an uber-issue to track python work in this space. Here're the sub-tasks:

• [ ] https://github.com/Azure/azure-sdk-for-python/issues/36779

• Cleanups and breaking changes

  • [ ] [P2] Set az.namespace, client library name and version on tracer instrumentation scope
  • [ ] [P0] https://github.com/Azure/azure-sdk-for-python/issues/9256
  • [ ] [P1] https://github.com/Azure/azure-sdk-for-python/issues/9079

• [ ] Testing

  • [P2] User study if we can find someone internal
  • [P1] Integration tests for AMQP SDKs, retries, attributes
  • [P1] Perf testing: e.g. run storage perf tests with tracing enabled.
  • [P3] Sample will latest and greatest OTel and AppInsights SDK/AzMon exporter including AMQP and HTTP SDK. - Here's the existing draft https://github.com/lmolkova/azuresdk_tracing_demo/tree/python

• [ ] Misc

  • [P0] Update docs
  • [P2] Add tracing to common TSG

[azure-sdk]

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Monitor - Exporter:0.33717316,Event Hubs:0.15609778,Service Bus:0.096411765'

[lzchen]

Can Set client library name and version on tracer instrumentation scope be scoped into the GA milestone as a must have? It would be great we knew on the span level (populated by tracer instrumentation scope) which azure-sdk service was responsible for generating it. @pvaneck would this be a lot of work?

[github-actions[bot]]

Hi @lmolkova, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.