David Ashpole

/triage accepted /assign @stevehipwell

Hey, I work on the OpenTelemetry collector's prometheus components. Can you share the full error message, including which collector component it is coming from? I suspect this is a bug...

That does look like a bug in the collector's prometheus exporter. Per the [OTel specification](https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/#metric-metadata-1): > Exporters MUST drop entire metrics to prevent conflicting TYPE comments, but SHOULD NOT drop...

Filed https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/28617

/assign @dgrisonnet /triage accepted

I think this was a decision made early in its development that was never revisited. With the [pending archival](https://opentelemetry.io/blog/2023/sunsetting-opencensus/) of this and other OpenCensus repositories, I don't think we will...

The previous spec PR was closed in favor of https://github.com/open-telemetry/opentelemetry-specification/pull/2951, which is now merged. See https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#metricproducer for the MetricProducer spec, and https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#registerproducermetricproducer for the RegisterProducer(metricProducer) function on MetricReaders.

> The public handler would analyse whether metrics and traces are configured or not, and automatically load the appropriate handlers. How would this work? Is it possible to tell if...

/remove-lifecycle rotten

cc @Richabanker