David Ashpole

It probably isn't quite enough to meet the needs I have, but may be useful for others

Documenting a few experiments: * [Adding WithRegisterer](https://github.com/open-telemetry/opentelemetry-go/compare/new_sdk/main...dashpole:opentelemetry-go:prometheus_experiment) seems about the same in terms of ease-of-use as what we have now. * Making the exporter also an http handler does remove...

I had to move the opencensusmetric/internal package because it wasn't accessible from where I wanted to place the bridge...

rebased on the test fix

I think we should wait on this. I was able to discuss this at the prom wg yesterday ([notes](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/13117#issuecomment-1261065219)), and we concluded that we should see if it is possible...

While writing up the issue, i've realized that knowing openmetrics vs prometheus won't help us. I was going to write: > The OpenTelemetry collector's prometheus receiver is implemented as an...

This is now rebased on main (from the new_sdk/main branch)

cc @AbhiPrasad, who is listed as the codeowner

What resource attributes are attached to your OTLP metrics when you send them? The set of resource attributes should uniquely identify the sender, otherwise there would be collisions even if...

also cc @Aneurysm9