Recordsgolanggo.opentelemetry.io/otel/sdk/metric
Change the conditions
Current conditions
NewMeterProvider @v1.43.0linux · x64 · go 1.26 · go
1 of 11 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 146 / 157
- Contract verifications
- 1 / 11
- Independent reporting peers
- 3
- Last recorded
- 2026-09-08
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
0 of 10 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.43.0
linux · go@1.26
4 FAIL
· stage: UNKNOWN
· fingerprint: sha256:69d280c75213cffbfefa3920bca150e41e4eb0ce94d677766c799d026fb7e8fa
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 46 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 44 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 44 project-days |
| go.opentelemetry.io/otel | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 46 project-days |
| go.opentelemetry.io/otel/metric | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 46 project-days |
| go.opentelemetry.io/otel/sdk | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 46 project-days |
| go.opentelemetry.io/otel/trace | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 46 project-days |
| github.com/go-logr/stdr | v1.2.2 | PASS All observations passed | contract passed | 46 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: 8 · unchanged at every release: 1
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.