CodeSampleX

Recordsgolanggo.opentelemetry.io/contrib/instrumentation/net/http/otelhttpv0.71.0go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.WithSpanNameFormatter

Change the conditions
Fixed
Package versionv0.71.0 Symbolgo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.WithSpanNameFormatter
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.WithSpanNameFormatter @v0.71.0ubuntu glibc · x64 · go 1.26 · go 1

0 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 0

First observed break

v0.71.0

linux · go@1.26

2 FAIL · stage: UNKNOWN · fingerprint: sha256:52ffb5863abb9b322f1c5f3b82f86c4f2a4aec562912cda49e31e0429d7fd588

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/felixge/httpsnoop v1.1.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/stretchr/testify v1.12.1 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
go.opentelemetry.io/otel v1.46.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/metric v1.46.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/sdk v1.46.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/sdk/metric v1.46.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/trace v1.46.0 CANDIDATE Correlated change; unproven combination contract passed 2 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.

Libraryv0.71.0v0.70.0v0.68.0
github.com/felixge/httpsnoop v1.1.0 v1.1.0 v1.0.4
github.com/stretchr/testify v1.12.1 v1.11.1 v1.11.1
go.opentelemetry.io/otel v1.46.0 v1.45.0 v1.43.0
go.opentelemetry.io/otel/metric v1.46.0 v1.45.0 v1.43.0
go.opentelemetry.io/otel/sdk v1.46.0 v1.45.0 v1.43.0
go.opentelemetry.io/otel/sdk/metric v1.46.0 v1.45.0 v1.43.0
go.opentelemetry.io/otel/trace v1.46.0 v1.45.0 v1.43.0

Moved: 7 · unchanged at every release: 0

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