tint
🌈 slog.Handler that writes tinted (colorized) logs (by lmittmann)
logrus
Structured, pluggable logging for Go. (by sirupsen)
tint | logrus | |
---|---|---|
5 | 32 | |
600 | 24,078 | |
- | - | |
5.9 | 3.0 | |
about 1 month ago | about 1 month ago | |
Go | Go | |
MIT License | MIT License |
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.
tint
Posts with mentions or reviews of tint.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-05.
- Slogor: The colorful slog handler is now stable with version 1.1.2!
-
Slog: Zero-dependency structured logging in Go
A guide covering how to write custom handlers is out of scope for this post, but you can find one such guide written by the author of slog here. Thankfully, you don’t need to write a handler from scratch to use one. There are several community-contributed handlers, including handlers that allow you to output colored logs, and a handler that lets you implement sampling. You can find a full list here.
- slog module, colorize output based on level
- [Golang] tint: 🌈 slog.Handler that writes tinted logs
- tint: 🌈 slog.Handler that writes tinted logs
logrus
Posts with mentions or reviews of logrus.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-02.
-
Authentication system using Golang and Sveltekit - Initialization and setup
It's some sort of logging system well explained by Alex Edwards in Let’s Go Further. As stated, we could have used logrus or any other popular logging system in Go.
-
Renaming public Go modules
Option 2, please. You may not have been around for the logrus debacle, but it was a giant pain.
- What is the common log library which is industry standard that is used in server applications?
-
Observing AWS Lambda with Golang and Datadog
For the example I’m using the very popular logrus library and then I’m setting the log formatter to be JSON
-
Best Logging Library for Golang
For choosing the candidates for the poll, I didn't do any thorough research. I was looking for a library to use in my project at work, and I ended up at sirupsen/logrus which was already being used by one of the dependencies in that project.
-
Follow up to previous post: I contributed to an open source project outside working hours despite being asked not to. I was fired. No legal action.
I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.
-
Sourcehut will blacklist the Go module mirror
If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...
-
Lies we tell ourselves to keep using Golang
Like, for example, some projects importing logrus with a capital L and some with a lowercase L, and go modules having no way to reconcile the two: https://github.com/sirupsen/logrus/issues/553
-
go-coffeeshop - A practical coffee shop application event-driven microservices built with Golang
Ugh. Wish people would stop using logrus. It’s in maintenance mode and slow, especially its stack tracing.
- Criando uma API Rest com Fiber - Uma história pessoal de aprendizado
What are some alternatives?
When comparing tint and logrus you can also consider the following projects:
slogmw - Middleware for the go standard library log/slog package
zap - Blazing fast, structured, leveled logging in Go.
zax - Zap logger with context
zerolog - Zero Allocation JSON Logger
slog-sampling - 🚨 slog sampling: drop repetitive log records
glog - Leveled execution logs for Go
termenv - Advanced ANSI style & color support for your terminal applications
lumberjack - lumberjack is a log rolling package for Go
kemba - A tiny debug logging tool. Ideal for CLI tools and command applications. Inspired by https://github.com/visionmedia/debug
slog
glo - Logging library for Golang
log15 - Structured, composable logging for Go