logutil
Utils for use with zerolog (by mozey)
xtrace
A simple library to extract traces from golang's xerrors (by ollien)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
logutil
Posts with mentions or reviews of logutil.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-23.
-
Error stack traces in Go with x/xerror
> At boundaries between our code and calls out to external packages, make an effort to always wrap the result with xerrors.Errorf. This ensures that we always capture a stack trace at the most proximate location of an error being generated as possible
I've been doing something similar for a while using `errors.WithStack` from https://github.com/pkg/errors
The error can then be logged with https://github.com/rs/zerolog like this `log.Error().Stack().Err(err).Msg("")`
And using a console writer it's possible to get human readable output instead of the standard JSON, see https://github.com/mozey/logutil
xtrace
Posts with mentions or reviews of xtrace.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-23.
-
Error stack traces in Go with x/xerror
Like the article mentions, they didn't bring over stack traces (namely the `Formatter` interface) from xerrors. I wrote a library[1] around it that would generate true stack traces. I don't use it as much as I used to, because I don't want to depend on a package like xerrors I don't trust to remain maintained, but it was a fun exercise at the time, and very useful while I used it. I wish that we wouldn't have to depend on a tool like Sentry for bringing this about, like the author suggests.
https://github.com/ollien/xtrace
What are some alternatives?
When comparing logutil and xtrace you can also consider the following projects:
backward-cpp - A beautiful stack trace pretty printer for C++
errcode
errors - Go error library with error portability over the network
json-logs - A tool to pretty-print JSON logs, like those from zap or logrus.
zerolog - Zero Allocation JSON Logger
golangci-lint - Fast linters Runner for Go
go - The Go programming language