go.opentelemetry.io/otel/trace.SpanFromContext
third-partyThe 1894th most-called third-party function by production calls. Called 374 times across 67 modules; 324 of those run outside tests and generated code.
All of go.opentelemetry.io/otel/trace → Docs on pkg.go.dev ↗
- prod calls
- 324
- non-test, non-generated
- all calls
- 374
- total callsites
- modules
- 67
- distinct callers
- in loop
- 3%
- of prod calls
- in tests
- 13%
- 50 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function98%A direct call to an exported package function, resolved by type.
- Package function (by syntax)2%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into SpanFromContext from notable Go projects. Open one on the map to see what else it hammers.
- Grafana 91 28%
- Docker 27 8%
- OpenTelemetry 11 3%
- Kubernetes 8 2%
- Vault 7 2%
where it's called
Callsites in the wild
12 representative callsites of 374, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop test
- in loop test
top callers
The modules that reach for it
The modules that call SpanFromContext most in this snapshot.
- github.com/grafana/loki/v34913%
- github.com/grafana/pyroscope3910%
- github.com/ory/kratos308%
- github.com/dagger/dagger216%
- github.com/moby/buildkit205%
siblings
More from go.opentelemetry.io/otel/trace
The other most-called functions in this package. See all →