[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:

• Metrics SDK: allow metric readers to filter Meters during Collect() opentelemetry-specification#3617
  • prevents deployment of yaml configuration
  • cc @jack-berg
  • blocks implementation of:
    • [Feature] Metrics SDK: allow metric readers to filter Meters during Collect() #2709
• Metrics SDK: allow several metric readers to share the same metric exporter opentelemetry-specification#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:
    • [Performance] Avoid duplication of metric exporters. #2710
• Receive OTLP HTTP metrics, forward to Prometheus, collision on metric names opentelemetry-collector-contrib#21471
  • prevents deployment of OTLP Metrics exporter:
    • when sending data thru opentelemetry-cpp --> opentelemetry-collector --> prometheus,
    • prometheus metrics collides, breaking visualization
• Use Context to stop tracing opentelemetry-specification#530
  • hinders deployment of OTLP GRPC exporter

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.

[github-actions]

This issue was marked as stale due to lack of activity.