David Ashpole
David Ashpole
I noticed some confusion on this point in https://docs.google.com/document/d/1ZaFr8qbCpOZqnX7ItnLLg6S4NMwF3SiUuM5yBm4sIYY/edit#heading=h.v38n4whtu270. We should clarify in the limitations section of the README that the bridge does not support views.
### Problem Statement Examples currently only use stdout exporters, which is great for running things locally. I've often wanted to take our examples, and try them out with the collector,...
## Background At one point, I had written an OTep about how kubernetes resource detectors should function, but it wasn't accepted due to lack of interest. https://github.com/open-telemetry/oteps/pull/195 I was recently...
## Description Update OpenTelemetry dependencies, and follow best-practices for handling resource established in https://github.com/open-telemetry/opentelemetry-go/pull/4887. ## Checklist - [x] I have followed [Contributing Guidelines from CONTRIBUTING.MD](https://github.com/GoogleCloudPlatform/golang-samples/blob/main/CONTRIBUTING.md) - [x] **Tests** pass: `go...
**Client** logging: https://github.com/googleapis/google-cloud-go/tree/main/logging **Current behavior** The current implementation of populateTraceInfo always uses a remote span context as the parent https://github.com/googleapis/google-cloud-go/blob/ac16144215f844294c29063776f2f116e14ecebb/logging/logging.go#L807-L838 By "Remote span context", I mean a trace ID and...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3700 ## Changes The current specification mixes OpenMetrics and Prometheus in ways that can be confusing. This change first explains the differences between various Prometheus formats, and then consistently...
Closes https://github.com/open-telemetry/opentelemetry-specification/issues/3303 ## Changes From @tigrannajaryan in https://github.com/open-telemetry/opentelemetry-specification/issues/3303#issuecomment-1967252364: > I think the conclusion in https://github.com/open-telemetry/opentelemetry-specification/issues/3518 was that we keep the names. It has been a while and there is no...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3702 Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/2468 Addresses https://github.com/open-telemetry/opentelemetry-specification/issues/3737#issuecomment-1787439083 Depends on https://github.com/open-telemetry/opentelemetry-specification/pull/3871 (docfx check will fail until this is rebased on it) ## Changes * Add option to disable `target` info metric. *...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3058 Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/1712 Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/2409 ## Changes Use metric.metadata (added in https://github.com/open-telemetry/opentelemetry-proto/pull/514) to support representing prometheus metric types in OTLP. ### Alternative Considered We could consider using a metadata...
This is a tracker for stabilizing this specification, which is currently experimental: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md There are currently three compliant SDK implementations, per the [compliance matix](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#exporters): Go, Java, Rust. The prometheus receiver...