[TRACKING] List of upstream issues impacting opentelemetry-cpp

TO @open-telemetry/technical-committee
TO @open-telemetry/specs-metrics-approvers
CC @svrnm

All,

The following issues are affecting opentelemetry-cpp, and hinder progress:

• https://github.com/open-telemetry/opentelemetry-specification/issues/3617
  • prevents deployment of yaml configuration
  • cc @jack-berg
  • blocks implementation of:
    • https://github.com/open-telemetry/opentelemetry-cpp/issues/2709
• https://github.com/open-telemetry/opentelemetry-specification/issues/3616
  • Current posture is to:
    • either implement knowingly not compliant code in opentelemetry-cpp, as in java
    • or comply to the spec, and limit the usefulness of opentelemetry-cpp
  • blocks implementation of:
    • https://github.com/open-telemetry/opentelemetry-cpp/issues/2710
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21471
  • prevents deployment of OTLP Metrics exporter:
    • when sending data thru opentelemetry-cpp --> opentelemetry-collector --> prometheus,
    • prometheus metrics collides, breaking visualization
• https://github.com/open-telemetry/opentelemetry-specification/issues/530
  • hinders deployment of OTLP GRPC exporter

Using this issue for project tracking, until a better place for it can be found.

Start by reviewing upstream issues 3617, 3616, 21471, and 530, along with the blocked opentelemetry-cpp issues 2709 and 2710. Determine whether each upstream dependency is resolved and update the tracking issue when the configuration, metrics, or OTLP exporter blockers have a documented outcome.