glog
zap
Our great sponsors
glog | zap | |
---|---|---|
8 | 51 | |
3,508 | 20,762 | |
0.4% | 1.6% | |
5.5 | 8.1 | |
4 months ago | about 19 hours ago | |
Go | Go | |
Apache License 2.0 | 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.
glog
-
Best Logging Library for Golang
I started a poll on r/golang with these four candidates, but also came to know about glog which was a go port of a C++ project by Google. I used that option in the poll conducted on LinkedIn.
-
Have you replaced Sirupsen/logrus, and if so, with what?
Other than print and formatted print to stdout and stderr, what more do you need? I adapted much of the glog rationale into a logging wrapper. Allowing many thousands of unneeded lines from Logrus to be avoided. https://github.com/golang/glog
-
Backdooring Rust crates for fun and profit
By globals, I mean global resources outside of the codes namespace. It may not even be a resource in the process, such as a log file or temporary directory or a database. If you have two versions of a crate in their completely separate worlds, and call both of their init_logging() functions to log to a file specified by an environment variable, things are likely to go pear shaped when they stomp over each others log file.
I'm a Rust novice, but the example I tripped over in Go was https://github.com/golang/glog. It has a module level init() initialization routine that makes calls to the stdlib flags package, manipulating the default command line flags (a global resource). If you ended up with multiple versions of glog via transient dependencies, your program would panic on startup as the second version's init() would make calls only allowed to be called once. Rust thankfully avoids this particular one by requiring initialization to be called by main() (apart from the hack described in the article).
-
Lumber: A simple and pretty logger for Golang
There is no better way than looking at your older brothers and learning from them: stdlib log, glog, logrus, zerolog, log15 (eth fork)...
-
simple logging module for Go - Glog
Also glog is the name of Google logging library which is confusing. https://github.com/golang/glog
-
Simple leveled logging solution
the 5th hit looks like something made 6-8 yrs ago which would have worked: https://github.com/golang/glog
-
can someone review my code?
Read similar repos, compare, learn: https://github.com/rs/zerolog https://christine.website/blog/ln-the-natural-logger-2020-10-17 https://github.com/sirupsen/logrus https://github.com/golang/glog https://github.com/nikandfor/tlog (this one is mine)
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?
zax - Zap logger with context
logrus - Structured, pluggable logging for Go.
zerolog - Zero Allocation JSON Logger
slog
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.