zap
go-cmp
Our great sponsors
zap | go-cmp | |
---|---|---|
51 | 7 | |
20,762 | 3,935 | |
1.6% | 1.3% | |
8.1 | 3.7 | |
about 21 hours ago | 3 months ago | |
Go | Go | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zap
-
Building RESTful API with Hexagonal Architecture in Go
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
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.
Oof. We just converted all of our logging to zap[0] to get structured JSON logging for downstream parsing. Wonder how the perf stacks up.
-
Kubebuilder Tips and Tricks
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
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).
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/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
- Why it is so weirdo??
- What is the common log library which is industry standard that is used in server applications?
go-cmp
-
Visualizing Diffs The Myers difference algorithm
This made me think of a couple other interesting things:
1. you can change which algorithm is used in git diff as multiple are supported
https://luppeng.wordpress.com/2020/10/10/when-to-use-each-of...
2. Google has an edit graph implementation in Go in the cmp package
https://github.com/google/go-cmp/blob/master/cmp/internal/di...
-
How do you do DB preparation in e2e tests?
Assertion libraries that people seem to love: - testify (my favorite) - go-cmp is a more barebones library - gotest.tools -- I have never used this but some swear by it
-
alecthomas/assert: A minimalist type-safe drop-in replacement for testify/require
it uses https://github.com/google/go-cmp instead of reflect.DeepEqual
-
What annoys you about Go?
When I use functional arguments, I either prefix all of the options with the same prefix or put them in a dedicated package (like cmpopts) to help the IDE.
-
Migrating from PHP to Go
Checking for equality in tests: https://github.com/google/go-cmp
-
What are your favorite packages to use?
oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).
-
Go Package for Equality: github.com/google/go-cmp
One thing to keep in mind about reflect.DeepEqual is because of the way it is implemented you could get positive results when the values are not actually the same, see this comment for reference.
What are some alternatives?
logrus - Structured, pluggable logging for Go.
zerolog - Zero Allocation JSON Logger
slog
glog - Leveled execution logs for Go
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
go-log - a golang log lib supports level and multi handlers
log - Structured logging package for Go.
lumberjack - lumberjack is a log rolling package for Go
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
seelog - Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting.
go-grpc-middleware - Golang gRPC Middlewares: interceptor chaining, auth, logging, retries and more.
log15 - Structured, composable logging for Go