CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/exporters/stdout/stdoutmetricv1.46.0

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

○ 62026-08-31
ubuntu glibc
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric.Exporter 0%1
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric.New 75%8
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric.Option 60%5
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric.WithPrettyPrint 60%5
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric.WithWriter 75%8
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric.WithoutTimestamps 75%8

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Environment detail

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.

Environment Confidence Observations Verified Pass rate Peers Last seen
go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 1✓ 2✕ · PROJECT_PROCESS 4✓ · PROJECT_TEST 3✓ — Usage: USED 5✓
 MEDIUM 10 +5 0 80% 2 2026-08-31

Recent failure clusters

Symbols