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.
logr
- What is the common log library which is industry standard that is used in server applications?
-
Created a small logging library in Go.
logr
-
Logging Library
How about using https://github.com/go-logr/logr Youβll be able to swap concrete implementation easily which will allow you to try out different libs on the market without refactoring all your logic
-
Have you replaced Sirupsen/logrus, and if so, with what?
I recommend https://github.com/go-logr/logr and you can choose implementation freely but zerolog/zap are optimized for speed.
-
Version 1.18 Refresh for Go Programmers
For logging, I use https://github.com/go-logr/logr with https://github.com/uber-go/zap
- Golog: an extensible logger for Go
-
Logger and Clean Architecture
I'd say it depends. If I write a package for others to use I usually don't include a logger at all and let the user decide what he wants to use. For any other project that needs logging I usually skip the interface to not have the struggle with finding one interface that fits all at least logrus and zap. We kinda agreed at the team to just use zap by now. One.thing i wanted to try tho is using sth like logr which provides an interface for the most commonly used loggers.
-
Go Masterpieces
After writing a lot of libraries I really appreciate logr. There are plenty of times when my library needs to output debugging info, but it's not practical to do things like parse flags for verbosity level. With thus I can just log at a higher V level and be done with it.
tlog
-
Created a small logging library in Go.
Here is my list of stars related to observability. https://github.com/stars/nikandfor/lists/logs And this is what I have now https://github.com/nikandfor/tlog
-
Lumber: A simple and pretty logger for Golang
I did the same and now I have always developing tlog.
-
A few bytes here, a few there, pretty soon youβre talking real memory
https://github.com/nikandfor/tlog/blob/8d07c7ce58ad31f7000494affb016d6da5d7798b/unsafe.go#L15 https://github.com/nikandfor/tlog/blob/8d07c7ce58ad31f7000494affb016d6da5d7798b/encoder.go#L144 https://github.com/nikandfor/tlog/blob/8d07c7ce58ad31f7000494affb016d6da5d7798b/encoder.go#L214
- glog verbosity + urfave/cli/v2
What are some alternatives?
zerolog - Zero Allocation JSON Logger
trice - π’ super fast π and tiny π₯ embedded device πΎ printf-like trace β code, works also inside β‘ interrupts β‘ and real-time PC π» logging (trace ID visualization π)
zap - Blazing fast, structured, leveled logging in Go.
fgprof - π fgprof is a sampling Go profiler that allows you to analyze On-CPU as well as Off-CPU (e.g. I/O) time together.
life
logrus - Structured, pluggable logging for Go.
golog - Golog is a production ready logger which support tracing and other custom behaviours out of the box. Blazing fast and simple to use.
gf - GoFrame is a modular, powerful, high-performance and enterprise-class application development framework of Golang.
uftrace - Function graph tracer for C/C++/Rust/Python
log15 - Structured, composable logging for Go
glog - Leveled execution logs for Go