CodeSampleX

Recordsgolanggo.opentelemetry.io/otelv1.37.0go.opentelemetry.io/otel.GetTracerProvider

Change the conditions
Fixed
OSlinux Symbolgo.opentelemetry.io/otel.GetTracerProvider
Filter Runtimego 1.26 Package versionv1.37.0 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel.GetTracerProvider @v1.37.0linux · glibc · x64 · go 1.26 · go 1

1 of 1 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 1

First observed break

v1.37.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:deba6f972850caf602063f027430a9cb99f8772a48b20791481ad8d677afe94f

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.3 CANDIDATE Correlated change; unproven combination contract passed 75 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 75 project-days
github.com/stretchr/testify v1.10.0 CANDIDATE Correlated change; unproven combination builds observed 64 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
go.opentelemetry.io/auto/sdk v1.1.0 CANDIDATE Correlated change; unproven combination contract passed 75 project-days
go.opentelemetry.io/otel/metric v1.37.0 CANDIDATE Correlated change; unproven combination contract passed 75 project-days
go.opentelemetry.io/otel/trace v1.37.0 CANDIDATE Correlated change; unproven combination contract passed 75 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 75 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Libraryv1.46.0v1.45.0v1.44.0v1.43.0v1.37.0v1.35.0v1.34.0v1.28.0v1.24.0
github.com/go-logr/logr v1.4.4 v1.4.4 v1.4.3 v1.4.4 v1.4.3 v1.4.2 v1.4.2 v1.4.2 v1.4.1
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.6.0 — v0.6.0
github.com/stretchr/testify v1.12.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.10.0 — — v1.8.4
go.opentelemetry.io/auto/sdk v1.2.1 v1.2.1 v1.2.1 v1.2.1 v1.1.0 v1.1.0 v1.1.0 — —
go.opentelemetry.io/otel/metric v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.35.0 v1.34.0 v1.28.0 v1.24.0
go.opentelemetry.io/otel/trace v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.35.0 v1.34.0 v1.28.0 v1.24.0
github.com/cespare/xxhash/v2 v2.3.0 v2.3.0 v2.3.0 v2.3.0 — — — — —
github.com/go-logr/stdr v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2

Moved: 6 · unchanged at every release: 2

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters