samber / slog-zap Goto Github PK

By default, zap outputs to the logs the place where the logger was called from, but due to the fact that it is called from the internal handler, it outputs it incorrectly (not actual call location, but in internal handler).

e.g. output from readme example:
2024-01-08T12:46:03.534+0300 INFO [email protected]/handler.go:65 caramba! {"query.duration": "1s", "error": {"error":"could not count users","kind":"*errors.errorString","stack":null}

I know that you can set AddSource to true and get the same thing in additional argument, but I'm wondering if there is a way to fix or configure the output of call location for the default logger?

Currently, zap builds its own stacktrace and puts it in a string. It prevents us from playing with it and moving the initial frame to the slog logger call (instead of zap logger call).

We should write a stacktrace by ourselves. See the job done at https://github.com/samber/oops