David Ashpole

The prometheus exporter specification needs to be updated to clarify that it needs to follow the conversion specification.

@jack-berg Re: exponential histograms, i've tried to address that in https://github.com/open-telemetry/opentelemetry-specification/pull/3872. The basic idea is that exporters should be required to support the text format. But since the text format...

According to the [Prometheus-wg notes](https://docs.google.com/document/d/19bnXziPn2MZ9wO6684UoI4D-LCjGL5bTJkGhux29bx8/edit) from 11/8, @ywwg will be working on a migration plan, and will reach out when it is ready.

Proposal: https://github.com/prometheus/proposals/pull/30

From the prometheus wg discussion on 12/6/23, Prometheus exporters should support negotiation to determine if it should sanitize metric names and attributes. This will allow OpenTelemetry exporters to keep dots...

Yes, i'm working on a survey + panel with the end-user SIG to try to drive a resolution to the naming questions above.

Is this issue still being considered? I see https://github.com/elastic/ecs-logging-java/issues/214#issuecomment-1733893266, #3469, and #3518 suggest we are planning to keep the current field names. I'm interested in seeing https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/logging_trace_context.md reach stability, and...

PR: https://github.com/open-telemetry/opentelemetry-specification/pull/3909

/assign @rexagod /triage accepted

@MadVikingGod is there an issue tracking the work that needs to be done to get past the breaking changes in semconv? It looks like we do have v1.23.1 generated: https://github.com/open-telemetry/opentelemetry-go/pull/4749