David Ashpole

### Problem Statement After https://github.com/open-telemetry/opentelemetry-specification/pull/2951, and https://github.com/open-telemetry/opentelemetry-specification/pull/2979, we could implement a metric bridge for OpenCensus. Note that the specifications are experimental, so it isn't critical that it is implemented at...

The [current implementation](https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/opentelemetry-exporter-prometheus/src/PrometheusExporter.ts#LL44C25-L44C25) allows specifying a prefix which is globally applied to all metrics for the exporter. From the [OpenMetrics spec on target metadata](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#supporting-target-metadata-in-both-push-based-and-pull-based-systems): > Exposers MUST NOT prefix MetricFamily...

Prometheus exporter handles instrumentation scope and prevents collisions

4

Now that https://github.com/open-telemetry/opentelemetry-specification/pull/2703 is released, we can update the prometheus exporter to make use of OpenTelemetry scope, particularly for reducing collisions between metrics with the same name. **Describe the solution...

From the OTel prometheus [compatibility spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1): > The Unit of an OTLP metric point MUST be added as [OpenMetrics UNIT metadata](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#metricfamily). Additionally, the unit MUST be added as a suffix...

Support recording metrics with "churning" labels without "leaking" memory.

2

### Problem Statement I often want to record metrics about something which has unbounded (or bounded, but unreasonably high) cardinality across time, but has bounded cardinality within a time period...

### Description otel_scope_info and target_info should now only be generated when scope attributes and resource attributes are non-empty. From https://github.com/open-telemetry/opentelemetry-specification/pull/3660: > Prometheus exporters SHOULD generate an [Info](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#info)-typed metric named `otel_scope_info`...

MetricProducer support

2

### Problem Statement https://github.com/open-telemetry/opentelemetry-specification/pull/2951 defined an experimental MetricProducer interface, which can be used to support metric bridges. Note that the specifications are experimental, so it isn't critical that it is...

Prometheus exporter: Add text-based tests

1

Improve testing of the Prometheus exporter by comparing the serialized output with expectations. In opentelemetry-go, tests are compared with the contents of a test file, such as https://github.com/open-telemetry/opentelemetry-go/blob/main/exporters/prometheus/testdata/gauge.txt This makes...

Prometheus exporter handles instrumentation scope and prevents collisions

2

Now that https://github.com/open-telemetry/opentelemetry-specification/pull/2703 is released, we can update the prometheus exporter to make use of OpenTelemetry scope, particularly for reducing collisions between metrics with the same name. **Describe the solution...

Follow-up to #4897