logrus
glog
Our great sponsors
logrus | glog | |
---|---|---|
32 | 8 | |
24,012 | 3,513 | |
- | 0.4% | |
3.0 | 5.5 | |
24 days ago | 15 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
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.
logrus
-
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
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
-
what go logging pkg that output/hides logs according to verbosity -v flag ?
check out glog, it supports flags out out the box
-
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)
What are some alternatives?
zap - Blazing fast, structured, leveled logging in Go.
zax - Zap logger with context
zerolog - Zero Allocation JSON Logger
lumberjack - lumberjack is a log rolling package for Go
slog
log15 - Structured, composable logging for Go
xlog - xlog is a logger for net/context aware HTTP applications
seelog - Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting.
log - Structured logging package for Go.