Blazing fast, structured, leveled logging in Go. (by uber-go)

Zap Alternatives

Similar projects and alternatives to zap

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better zap alternative or higher similarity.

zap reviews and mentions

Posts with mentions or reviews of zap. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-27.
  • Desvendando o package fmt do Go
    1 project | | 1 Nov 2023
  • Building RESTful API with Hexagonal Architecture in Go
    21 projects | | 27 Sep 2023
    The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
  • Structured Logging with Slog
    11 projects | | 22 Aug 2023
    It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.


  • Kubebuilder Tips and Tricks
    2 projects | | 22 Aug 2023
    Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
  • Go 1.21 Released
    7 projects | | 8 Aug 2023
    What else would you expect from a structured logging package?

    To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).

    The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.

    I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).



  • Efficient logging in Go?
    1 project | /r/golang | 11 Jun 2023
  • Why elixir over Golang
    10 projects | /r/elixir | 29 May 2023
    And finally for structured logging:
  • Beginner-friendly API made with Go following hexagonal architecture.
    5 projects | /r/golang | 21 May 2023
    For logging: I recommend using Uber Zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
  • slogx - slog package extensions and middlewares
    3 projects | /r/golang | 1 May 2023
  • Why it is so weirdo??
    2 projects | /r/ProgrammerHumor | 22 Mar 2023
  • A note from our sponsor - InfluxDB | 20 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →


Basic zap repo stats
7 days ago

uber-go/zap is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of zap is Go.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives