David Ashpole

I would also prefer not to copy as much of the prometheus codebase if we can avoid it.

Regarding https://github.com/open-telemetry/opentelemetry-go/issues/3405#issuecomment-1294359346, the query to join a metric with target_info should look something like: `my_metric * on(instance, job) group_left(service_name, service_version, etc) target_info` It should be possible to use recording rules...

The exporter currently follows the opentelemetry specification for prometheus exporters. If the current behavior needs to be changed, we should open an issue in the specification repo. The solutions discussed...

@kernelpanic77 let me know if you need any help with this, as it is fairly complex. For reference, the spec for this is: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#exemplars-1 > [Exemplars](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/data-model.md#exemplars) on OpenTelemetry Histograms and...

I'll work on this one, if thats alright

Sorry for the slow response. That does look like a bug. Feel free to open a PR with a fix, and we can get it merged.

I'll write the document for the prometheus compatibility WG. I hope to wrap up the WG in the next few months.

/assign @rexagod /triage accepted From the sig meeting: this should happen sometime this month. Blocked by a protobuf dependency in prometheus.

/assign @dgrisonnet /triage accepted

/assign @pwittrock /triage accepted