Tyler Yahn

@Omkar-Waingankar I would recommend holding of on this issue until we have a more stable SDK. There are still incoming changes in the instrument provider that would affect any caching...

Is this a request related to the [`otelhttp`](https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp) instrumentation?

@MadVikingGod is going to look into what metrics should be added and the feasibility of this feature.

It looks like the added test is quite flaky or does not succeed on windows: https://github.com/open-telemetry/opentelemetry-go/actions/runs/3380083340/jobs/5613037464 We need our testing system to be solid and therefore this needs to be...

Looks like the tests are still failing: https://github.com/open-telemetry/opentelemetry-go/actions/runs/3586714280/jobs/6036245937 I'm more in favor of stable testing than accepting these changes as is.

This is a know difference between [this projects versioning and stability policy](https://github.com/open-telemetry/opentelemetry-go/blob/main/VERSIONING.md#policy) and the Go language. It is something inherited from the OpenTelemetry project itself. It is not something we...

> I'm raising this because I'm concerned as a potential user of this API. If I decided to implement a `Tracer` using the API and interface currently provided, then many...

> @MrAlias Do you feel that this issue could be re-opened, given the discussion currently being had, or is this a firm rule that this library has chosen to take?...

For those who would like this project to not extend API interfaces, please make sure your voice is heard in the specification issue to add a new method to the...

@kernelpanic77 it looks like it does: https://github.com/open-telemetry/opentelemetry-go/blob/d9d9507227b30ad83500ec59e5714d0314ac83be/exporters/prometheus/exporter.go#L252 Should I assign it to you?