CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/exporters/prometheusfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

# example.com/sample/test …

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-30 · Last seen: 2026-08-30

sha256:09d24b1b4448…

go.opentelemetry.io/otel/exporters/prometheus.New go.opentelemetry.io/otel/exporters/prometheus.WithNamespace go.opentelemetry.io/otel/exporters/prometheus.WithoutCounterSuffixes go.opentelemetry.io/otel/exporters/prometheus.WithoutScopeInfo go.opentelemetry.io/otel/exporters/prometheus.WithoutTargetInfo go.opentelemetry.io/otel/exporters/prometheus.WithoutUnits

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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: 3

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.

Evidence gaps

Published answers for the affected releases

Back to the package