David Ashpole

Consider using go module paths for scope name in demos

3

### Problem Statement I noticed the rolldice example has a single-word name for the meter and tracer: https://github.com/open-telemetry/opentelemetry-go/blob/ca93aae3e9f6922f623d193fac84b13f26dfc0b3/example/dice/rolldice.go#L12-L17 I haven't checked other examples, but IMO we should consider doing this...

Move time.Now call into exemplar reservoir to improve performance

8

Part of addressing https://github.com/open-telemetry/opentelemetry-go/issues/5542. ### Motivation This removes the `time.Now()` call from filtered-out Exemplars by only invoking `time.Now()` after the filtering decision is made. This improvement is especially noticeable for...

Make it easier to add a resource resource.Detector to the SDKs

3

### Problem Statement There is a fairly common use-case which users need to do when configuring the (trace/metric/logs) SDK, in which they want to add a resource detector for the...

Implement new runtime metrics

6

Part of https://github.com/open-telemetry/opentelemetry-go-contrib/issues/5655 Changes: * Move the configuration options to `options.go` without modification. * Implements the metrics defined here: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/runtime/go-metrics.md. These are still disabled by default while it is under...

### Problem Statement Follow-up to https://github.com/open-telemetry/opentelemetry-go/issues/4993 Context: https://github.com/kubernetes/kubernetes/issues/103186 I would like otelhttp to allow me to pass the start time using the go `context.Context`. This lets me move my instrumentation...

Add Distributed Tracing using OpenTelemetry

17

Prior issues/PRs related to distributed tracing: https://github.com/etcd-io/etcd/issues/11166, https://github.com/etcd-io/etcd/issues/9242, https://github.com/etcd-io/etcd/pull/5425. In the kubernetes instrumentation sig, we are adding working to add Distributed Tracing support using OpenTelemetry to the kube-apiserver: [kubernetes/enhancements/keps/sig-instrumentation/647-apiserver-tracing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/647-apiserver-tracing). We...

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...

### Context Found as part of https://github.com/open-telemetry/opentelemetry-python/pull/3924. The [semantic conventions for instrument unit](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/metrics.md#instrument-units) recommend using annotations, rather than the unity: > Instruments that measure an integer count of something SHOULD...

Consider support for testing exemplars in prometheus/testutil

4

Context: https://github.com/open-telemetry/opentelemetry-go/pull/5111 I am in the process of adding exemplar support to the OpenTelemetry-go prometheus exporter. We currently use [testutil.GatherAndCompare](https://github.com/prometheus/client_golang/blob/50ab457fb7e73866c181943e1aaf88ee0ccacc61/prometheus/testutil/testutil.go#L202) for most of our testing, as it makes it easy...

Add Prometheus compatibility survey blog

13

The raw results are here: https://github.com/open-telemetry/sig-end-user/tree/b5cb097ca529cea62809d5078ef8e30a54ad86b9/end-user-surveys/otel-prom-interoperability Similar to the collector survey, i've written a blog post summarizing the results. @open-telemetry/wg-prometheus