golang.org/x/net/trace.EventLog.Printf
third-partyThe 7322nd most-called third-party method by production calls. Called 82 times across 5 modules; 81 of those run outside tests and generated code.
- prod calls
- 81
- non-test, non-generated
- all calls
- 82
- total callsites
- modules
- 5
- distinct callers
- in loop
- 32%
- of prod calls
- in tests
- 1%
- 1 calls
- resolved
- 0%
- 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 →
- Interface method100%Called through an interface. The runtime target may differ.
who calls this
Notable callers
Production calls into EventLog.Printf from notable Go projects. Open one on the map to see what else it hammers.
- Dgraph 64 79%
where it's called
Callsites in the wild
12 representative callsites of 82, prioritizing in-loop and non-test usage. We link to source, never display it.
-
dgraph-io/badger @v1.6.2
in loop - in loop
-
dgraph-io/badger @v1.6.2
in loop - in loop
-
dgraph-io/badger @v1.6.2
in loop - in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
top callers
The modules that reach for it
The modules that call EventLog.Printf most in this snapshot.
- github.com/dgraph-io/badger2429%
- github.com/dgraph-io/dgraph2328%
- github.com/dgraph-io/dgraph/v241721%
- github.com/hypermodeinc/dgraph/v241721%
- golang.org/x/net11%