News for hackers. Stuff that matters.

A comment on Structured Logging with Slog. Parent comment

Re:Structured Logging with Slog by jupp0r on Tuesday August 22, 2023 @03:41PM (#37227593)
I think Uber chose a better approach for their Go logging library called Zap [1]

    logger.Info("failed to fetch URL",
      // Structured context as strongly typed Field values.
      zap.String("url", url),
      zap.Int("attempt", 3),
      zap.Duration("backoff", time.Second),
    )
They also have zap.Error(err) which generates the "error" key as a convention.

[1] https://github.com/uber-go/zap

[ Parent | on HN ]
Re:Structured Logging with Slog by bpicolo on Tuesday August 22, 2023 @04:00PM (#37227804)
As mentioned in the article, Zap's SugaredLogger has roughly the same thing https://pkg.go.dev/go.uber.org/zap

    sugar.Infow("failed to fetch URL",
      "url", "http://example.com",
      "attempt", 3,
      "backoff", time.Second,
    )
Really slog presents mostly the same two APIs as Zap, with a single entrypoint.
[ Parent | on HN ]
Re:Structured Logging with Slog by Groxx on Tuesday August 22, 2023 @07:55PM (#37230136)
`[level]w` supports both key/value pairs and individual `zap.Type(key, value)` values combined fwiw, so for that part the API is essentially the same too
[ Parent | on HN ]
Re:Structured Logging with Slog by masklinn on Tuesday August 22, 2023 @04:24PM (#37228057)
Slog allows doing that by creating Attr structs directly.
[ Parent | on HN ]
Re:Structured Logging with Slog by sa46 on Tuesday August 22, 2023 @07:48PM (#37230083)
You can reproduce that example with slog verbatim by changing zap to slog.

For example: https://pkg.go.dev/golang.org/x/exp/slog#example-Group

[ Parent | on HN ]