David Ashpole

> Would an alternative here would be to strip the prefix from the prometheus generated metrics via feature gate move towards using target_info to provide a namespace? I'm not sure...

I've liked when the scope name is actually a link to the godocs for the package (e.g. go.opentelemetry.io/collector/exporter/exporterhelper). It removes any ambiguity for someone trying to figure out where the...

You can use OpenMetrics today with the prometheus exporter. In the example, you can change this line: https://github.com/open-telemetry/opentelemetry-go/blob/0e874c3468c2cbc5bbaf075537be6c0f2152b5ef/example/prometheus/main.go#L93 To: ```golang http.Handle("/metrics", HandlerFor(prometheus.DefaultGatherer, HandlerOpts{EnableOpenMetrics: true})) ```

I don't think this blocks the prometheus exporter GA. Adding UNIT metadata to the exporter after the go client has support can be done as an addition later.

Blocked by https://github.com/prometheus/client_golang/issues/684

> I think we could extend the specification to support timestamp resets, to support more aggressive removal of stale cumulative temporality data. That makes sense to me from a "keep...

Discussed this at the SIG meeting today: We will move forward with the proposal above. I will work on implementing it.

Are you able to provide the contents of curling the prometheus endpoint? Reading the implementation, I don't see anything that would obviously be the culprit for this.

You can (relatively easily) work around this using asynchronous gauges: ```golang func ExampleSynchronousGauge() { myGauge := NewFloat64Gauge() _, err := meter.Float64ObservableGauge( "my.metric.name", metric.WithUnit("s"), metric.WithInt64Callback(myGauge.Callback), ) if err != nil {...

I don't think this should block the prometheus exporter's GA.