Tracking issue: SDK Prometheus exporter spec-compliance

[dashpole]

I did a mini-audit of the current state of prometheus exporters in the OTel ecosystem a little while back. I'm leaving a tracking issue here to be able to easily see how those issues are progressing.

Go is compliant

Java:

• https://github.com/open-telemetry/opentelemetry-java/issues/5014
• https://github.com/open-telemetry/opentelemetry-java/issues/5015

Python:

• https://github.com/open-telemetry/opentelemetry-python/issues/3071
• https://github.com/open-telemetry/opentelemetry-python/issues/3072
• https://github.com/open-telemetry/opentelemetry-python/issues/3073

JS:

• https://github.com/open-telemetry/opentelemetry-js/issues/3463
• https://github.com/open-telemetry/opentelemetry-js/issues/3464
• https://github.com/open-telemetry/opentelemetry-js/issues/3465
• https://github.com/open-telemetry/opentelemetry-js/issues/3466
• https://github.com/open-telemetry/opentelemetry-js/issues/3467

C++:

• https://github.com/open-telemetry/opentelemetry-cpp/issues/1840
• https://github.com/open-telemetry/opentelemetry-cpp/issues/1841
• https://github.com/open-telemetry/opentelemetry-cpp/issues/1842
• https://github.com/open-telemetry/opentelemetry-cpp/issues/1843

.NET:

• https://github.com/open-telemetry/opentelemetry-dotnet/issues/3972
• https://github.com/open-telemetry/opentelemetry-dotnet/issues/3973
• https://github.com/open-telemetry/opentelemetry-dotnet/issues/3974
• https://github.com/open-telemetry/opentelemetry-dotnet/issues/3975

Rust:

• https://github.com/open-telemetry/opentelemetry-rust/issues/926
• https://github.com/open-telemetry/opentelemetry-rust/issues/927
• https://github.com/open-telemetry/opentelemetry-rust/issues/928
• https://github.com/open-telemetry/opentelemetry-rust/issues/929
• https://github.com/open-telemetry/opentelemetry-rust/issues/930

Swift:

• https://github.com/open-telemetry/opentelemetry-swift/issues/353
• https://github.com/open-telemetry/opentelemetry-swift/issues/354
• https://github.com/open-telemetry/opentelemetry-swift/issues/355
• https://github.com/open-telemetry/opentelemetry-swift/issues/356
• https://github.com/open-telemetry/opentelemetry-swift/issues/357
• https://github.com/open-telemetry/opentelemetry-swift/issues/358
• https://github.com/open-telemetry/opentelemetry-swift/issues/359
• https://github.com/open-telemetry/opentelemetry-swift/issues/360
• https://github.com/open-telemetry/opentelemetry-swift/issues/361

@open-telemetry/wg-prometheus

[marcalff]

@dashpole

Please also track the prometheus exporters located in the opentelemetry-collector.

• https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/prometheusexporter
• https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/prometheusremotewriteexporter

Use case:

• an application is instrumented to emit metrics
• exports metrics using the OTLP exporter (not Prometheus)
• to an opentelemetry-collector
• which forwards the data to prometheus

[dashpole]

Related OpenTelemetry Collector issues:

• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/16207
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8516
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8355
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8353
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8351
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8265
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/5192
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8950
• https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21743

[gouthamve]

Go has a couple of issues: https://github.com/open-telemetry/opentelemetry-go/issues/4371 and https://github.com/open-telemetry/opentelemetry-go/issues/4372