Records/golang/go.opentelemetry.io/otel/trace/v1.45.0/go.opentelemetry.io/otel/trace.NewTracerConfig

shared with 2 packages — this evidence cannot say whose API it is

Published samples

• go.opentelemetry.io/otel v1.45.0: Multiple WithInstrumentationAttributes and WithInstrumentationAttributeSet options merge scope attributes with last-value-wins precedence instead of overwriting earlier options Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.opentelemetry.io/otel/trace.NewTracerConfiggo.opentelemetry.io/otel/trace.WithInstrumentationAttributesgo.opentelemetry.io/otel/trace.WithInstrumentationAttributeSetgo.opentelemetry.io/otel/trace.TracerConfig.InstrumentationAttributesgo MIT-0 · 2026-08-16

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-08-31

Failure clusters

• observed PROJECT_TEST Evidence gap ×2 v1.35.0 → v1.45.0 os=linux · runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-30
  Diagnostic re-verification candidate