CodeSampleX

Recordsgolanggo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcv0.67.0

Change the conditions
Fixed
OSalpine musl
Filter Runtimego 1.26 Package versionv0.67.0 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc @v0.67.0alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

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

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 19 · Steady 4

First observed break

v0.67.0

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:77fe18d3f1f3da538150722b77c1f86dc377316432a9a0361d43801e61ab51c2

Library Version Health Measured there Projects
go.opentelemetry.io/otel v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
go.opentelemetry.io/otel v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel v1.44.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/metric v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
go.opentelemetry.io/otel/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel/metric v1.44.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/sdk v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
go.opentelemetry.io/otel/sdk v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel/sdk v1.44.0 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
go.opentelemetry.io/otel/trace v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
go.opentelemetry.io/otel/trace v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel/trace v1.44.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.79.2 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
google.golang.org/grpc v1.81.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.82.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/grpc v1.83.2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/grpc v1.84.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
google.golang.org/protobuf v1.36.12 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/stretchr/testify v1.11.1 PASS All observations passed contract passed 10 project-days
go.opentelemetry.io/otel/sdk/metric v1.42.0 PASS All observations passed contract passed 5 project-days
go.opentelemetry.io/otel/sdk/metric v1.43.0 PASS All observations passed contract passed 3 project-days
go.opentelemetry.io/otel/sdk/metric v1.44.0 PASS All observations passed 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.

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