Arthur Silva Sens

[They are dropped](https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/#exponential-histograms:~:text=Min%20and%20Max%20are%20not%20used.) since Prometheus Histograms don't have these kinds of information in them.

Interesting comparison @cyrille-leclerc, I also noticed that we offer a different functionality in OTel-Collector-Contrib's Prometheus exporter[[1](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/prometheusexporter#:~:text=resource_to_telemetry_conversion%3A%0A%20%20%20%20%20%20enabled%3A%20true)] and Prometheus Remote Write exporter[[2](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/prometheusremotewriteexporter#:~:text=resource_to_telemetry_conversion%3A%0A%20%20%20%20%20%20enabled%3A%20true%20%23%20Convert%20resource%20attributes%20to%20metric%20labels)] The existing feature doesn't follow any of the recommended...

I appreciate the effort of keeping the spec consistent with Prometheus' existing configuration, so maybe we can update the spec by changing the recommended configuration from `with_resource_constant_labels` to `promote_resource_attributes`? I...

Ok, Cyrille and I talked offline, and there's a consistency problem between Prometheus and OTel configuration options. OTel accepts wildcards to include/exclude, while Prometheus doesn't. We'll need to figure that...

This was fixed by #35562, right?

Hi @songy23, do you mind adding the label to trigger the windows tests in that PR? :)

Hey @devarsh10, could you rebase your PR? I believe this will fix you CI failure

Nice start! It's a big change so the review will be made in several parts 😬 > As described in #6628, I have made the necessary changes for restructuring in...