[TRACKING] List of upstream issues impacting opentelemetry-cpp

[marcalff]

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

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

[svrnm]

@marcalff can you link each upstream issue with the relevant issue in opentelemetry-cpp (if they exist)

[marcalff]

@marcalff can you link each upstream issue with the relevant issue in opentelemetry-cpp (if they exist)

Done for the first 2.

For the problem with the collector -> prometheus write exporter, there is no issue in opentelemetry-cpp, as the cpp code behaves as expected. This was found when integrating an application that uses opentelemetry-cpp.