ASP.NET Prometheus exporters timeline

[craigta]

I'm using the ASP.NET OTEL Prom exporter and it has been working well for me and the integration is nice. I see the OTEL Prom exporter itself is in Development, but I'm curious if there is any anticipated timeline or details about what is needed to move it to the next phases according to the maturity document? I'd love to use it in our production services officially

[dmathieu]

This is probably a better fit for opentelemetry-dotnet.

[craigta]

Thank you @dmathieu -- I posted there here:
open-telemetry/opentelemetry-dotnet#6493 (comment)

And got pointed back here :) It seems the development tag is primarily driven by the status of the OTEL spec. Specifically, this page tagged as Development got called out:
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md

I see the list of differences between the OTEL format and Prom format, which is what I think makes it be tagged as Development? Wondering if there is an overall goal to bring up to parity with Prom which would I think remove the Development tag, or if those are not planned to be made priority, which case probably it will be in Development for the foreseeable future

[trask]

hi @craigta,

I'd love to use it in our production services officially

I'm not sure the dotnet repo policy, but in the Java repo, when an artifact is not declared stable, it doesn't necessarily mean it's not production ready, only that the public API may change without a major version update

[craigta]

Thanks, I checked the Java equal -- the Prom Exporter for Java and it is similarly tagged as Alpha, so seems that for this particular exporter they are aligned on them being considered pre-release as well. It does look like this component was tagged as Alpha in Java 5 years ago, so not sure how often those types of decisions are revisited

I agree that it could be considered production quality, even if the spec is not fully implemented. I'd be OK with that based on the current capabilities we are using, but not sure how those decisions are made. Any ideas?

https://www.javadoc.io/doc/io.opentelemetry/opentelemetry-exporter-prometheus/latest/io/opentelemetry/exporter/prometheus/package-summary.html

[trask]

I don't think know if this has been documented anywhere (production quality but not API stable), so probably would need to ask in the associated repo or slack channel.