go.opentelemetry.io/otel/trace/noop.NewTracerProvider
third-partyThe 8594th most-called third-party function by production calls. Called 164 times across 42 modules; 69 of those run outside tests and generated code.
All of go.opentelemetry.io/otel/trace/noop → Docs on pkg.go.dev ↗
- prod calls
- 69
- non-test, non-generated
- all calls
- 164
- total callsites
- modules
- 42
- distinct callers
- in loop
- 0%
- of prod calls
- in tests
- 58%
- 95 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 function90%A direct call to an exported package function, resolved by type.
- Package function (by syntax)10%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into NewTracerProvider from notable Go projects. Open one on the map to see what else it hammers.
- Kubernetes 17 25%
- Docker 8 12%
- Grafana 6 9%
- Jaeger 6 9%
- Prometheus 3 4%
where it's called
Callsites in the wild
12 representative callsites of 164, prioritizing in-loop and non-test usage. We link to source, never display it.
-
go/logging @v1.19.0
logging_test.go:735
in loop test - in loop test
-
k8s.io/kubernetes @v1.36.3
pkg/kubelet/images/image_gc_manager_test.go:940
in loop test - in loop test
- in loop test
- in loop test
- in loop test
- in loop test
-
connectrpc.com/otelconnect @v0.9.0
option.go:74
-
moby/moby @v28.5.2+incompatible
-
-
top callers
The modules that reach for it
The modules that call NewTracerProvider most in this snapshot.
- github.com/kubernetes/kubernetes2515%
- github.com/jaegertracing/jaeger1912%
- k8s.io/kubernetes1912%
- github.com/grafana/alloy117%
- go.opentelemetry.io/otel95%