go.uber.org/zap.Logger.Fatal
third-partyThe 3652nd most-called third-party method by production calls. Called 168 times across 14 modules; 163 of those run outside tests and generated code.
- prod calls
- 163
- non-test, non-generated
- all calls
- 168
- total callsites
- modules
- 14
- distinct callers
- in loop
- 2%
- of prod calls
- in tests
- 3%
- 5 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 →
- Concrete method100%A method on a value whose type is known exactly.
who calls this
Notable callers
Production calls into Logger.Fatal from notable Go projects. Open one on the map to see what else it hammers.
where it's called
Callsites in the wild
12 representative callsites of 168, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
-
gorse-io/gorse @v0.5.11
in loop - in loop
-
gorse-io/gorse @v0.5.11
in loop -
go.uber.org/zap @v1.28.0
logger_test.go:991
in loop test -
-
cadence-workflow/shard-manager @v0.0.0-20260730082237-cd61cc023ec2
-
dstotijn/hetty @v0.7.0
-
-
-
-
top callers
The modules that reach for it
The modules that call Logger.Fatal most in this snapshot.
- github.com/jaegertracing/jaeger6136%
- github.com/gorse-io/gorse5935%
- github.com/dstotijn/hetty117%
- github.com/uber/cadence95%
- github.com/cadence-workflow/cadence74%
siblings
More from go.uber.org/zap
The other most-called members in this package. See all →