noodlog
glog
noodlog | glog | |
---|---|---|
1 | 8 | |
44 | 3,512 | |
- | 0.1% | |
1.3 | 5.5 | |
about 1 year ago | 30 days ago | |
Go | Go | |
Apache License 2.0 | 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.
noodlog
-
zlog: Secure logger in Go to prevent output of sensitive/secret values
For example, github.com/gyozatech/noodlog provides a similar function, but it assumes conversion to JSON, and type information is lost in the output stage. Since zlog basically performs hiding while preserving the types, you can freely choose the format of the final output.
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?
MrZ's go-logger - :mag: Easy to use, extendable and super fast logging package for Go
zax - Zap logger with context
sqldb-logger - A logger for Go SQL database driver without modifying existing *sql.DB stdlib usage.
logrus - Structured, pluggable logging for Go.
zerolog - Zero Allocation JSON Logger
zap - Blazing fast, structured, leveled logging in Go.
slog
log15 - Structured, composable logging for Go
glg - Simple and blazing fast lockfree logging library for golang
xlog - xlog is a logger for net/context aware HTTP applications