David Ashpole

Sorry we didn't get to look at your issue. Are you still facing this? If you are, can you properly format your description so we can read the yaml? E.g....

/assign @yangjunmyfm192085 /triage accepted

/triage accepted /assign @dgrisonnet

/assign @ricardoapl

/assign @dgrisonnet /triage accepted

### Current Spec The [specification currently says](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1): > Prometheus SDK exporters MUST NOT allow duplicate UNIT, HELP, or TYPE comments for the same metric name to be returned in a...

@fstab Let me know if you need any help on the OTel side of things here.

Since this is a stabilization tracking issue, there are a few open issues related to cardinality limits: * https://github.com/open-telemetry/opentelemetry-specification/issues/3866 * https://github.com/open-telemetry/opentelemetry-specification/issues/3813 * https://github.com/open-telemetry/opentelemetry-specification/issues/3798 * https://github.com/open-telemetry/opentelemetry-specification/issues/3578 #3578 in particular seems important...

I saw the TC notes. Is there any particular feedback related to Prometheus we want? The [current spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#cardinality-limits) has drawbacks for prometheus users, but these likely apply to non-prometheus users...

Thanks @jack-berg. You are correct, and I didn't realize that was possible.