OpenTelemetry tracing plugin

[lmolkova]

This is an uber-issue to track C++ tracing work necessary to GA otel plugin.

[Ge] Tasks

Preview Give feedback

1. [azure-core-tracing-opentelemetry] Adopt OpenTelemetry HTTP semconv 1.23.0 #5162
   Client OpenTelemetry +2
2. [azure-core-tracing-opentelemetry] Adopt OpenTelemetry error.type attribute for logical calls #5163
   Client OpenTelemetry +2

Sub-tasks:

• Support telemetry schema versioning (attribute names). User should be able to set OTel schema version from an enum we provide and OTel plugin should map attribute names according to given version. OTel schema version

  • Set it on tracer's instrumentation scope
  • Support 1.17.0 initially only (TBD - will switch to latest by GA)
  • Map attribute names reported by SDKs to corresponding ones in configured schema version. Here's the current list https://github.com/azure/azure-sdk/blob/main/docs/tracing/distributed-tracing-conventions.yml
  • We'll add new versions every once in a while and users will be able to configure them.
  • Don't change attribute names in SDKs
  • [nice-to-have] Set client library name and version on tracer instrumentation scope

• Cleanups and breaking changes

  • Nested logical spans suppression by default (new guidelines) "When client method creates a new span and internally calls into other public client methods of the same or different Azure SDK, spans created for inner client methods MUST be suppressed, their attributes and events ignored. Nested spans created for REST calls MUST be the children of the outer client call span. Suppression is generally done by Azure Core."

• Testing

  • Perf testing: e.g. run storage perf tests with tracing enabled.
  • [nice-to-have] Sample app

• Misc

  • Update docs
  • [nice-to-have] Add tracing to common TSG

[github-actions]

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.