errors
DISCONTINUED
zap
Our great sponsors
errors | zap | |
---|---|---|
30 | 51 | |
7,511 | 20,762 | |
- | 1.6% | |
0.2 | 8.1 | |
over 2 years ago | 2 days ago | |
Go | Go | |
BSD 2-clause "Simplified" License | MIT 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.
errors
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
- Error handling and serializing
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
-
My next client wants to redevelop a java Webapp with go
pkg/errors or stdlib errors - Error handling, but I wrote my own package for that tailored to my projects' needs. (FYI primalskill/errors but please don't use it as it's not production-ready yet and it will change a lot)
-
What are some good open source project to read when learning Go?
https://github.com/pkg/errors - errors with stack traces
-
Anyone using github.com/pkg/errors for stack traces?
The pkg.go.dev page lists 14k+ projects importing it, but the Github repository has been archived which would seem to discourage use. I'm also not a huge fan of the naming conflict with the stdlib errors package. The README notes it went into maintenance mode but it appears this, too, has passed.
-
go-faster/errors: clear go error wrapping with caller (xerrors fork with Wrap)
The pkg/errors and xerrrors are not maintainted
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?
What are some alternatives?
logrus - Structured, pluggable logging for Go.
zerolog - Zero Allocation JSON Logger
slog
glog - Leveled execution logs for Go
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
journald - Go implementation of systemd Journal's native API for logging