logo alternatives and similar packages
Based on the "Logging" category.
Alternatively, view logo alternatives based on common mentions on social networks and blogs.
-
loggo
A logging library for Go. Doesn't use the built in go log standard library, but instead offers a replacement. -
rollingwriter
RollingWriter is an auto-rotate io.Writer implementation with multi policies to provide log file rotation. -
httpretty
Pretty-prints your regular HTTP requests on your terminal for debugging (similar to http.DumpRequest). -
ozzo-log
High performance logging supporting log severity, categorization, and filtering. Can send filtered log messages to various targets (e.g. console, network, mail). -
logur
An opinionated logger interface and collection of logging best practices with adapters and integrations for well-known libraries (logrus, go-kit log, zap, zerolog, etc). -
gologger
Simple easy to use log lib for go, logs in Colored Cosole, Simple Console, File or Elasticsearch. -
stdlog
Stdlog is an object-oriented library providing leveled logging. It is very useful for cron jobs. -
mlog
A simple logging module for go, with 5 levels, an optional rotating logfile feature and stdout/stderr output. -
go-cronowriter
A simple writer that rotate log files automatically based on current date and time, like cronolog. -
gomol
Gomol is a library for structured, multiple-output logging for Go with extensible logging outputs
Get performance insights in less than 4 minutes
Do you think we are missing an alternative of logo or a related project?
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
Sponsored
www.saashub.com
|
README
Logo
A simple logging library for golang.
[banner](./banner.png)
I wanted to have a logger that is easy configurable with various io.Writers and a simple active and color on / off switch, so I created it.
Explanation
A Logger object can hold multiple Receivers. Every Receiver holds an io.Writer object (f.e. os.File, os.Stderr), a Level which is minimal the log level that is logged, a boolean Active which says if the Receiver should log or not, and a boolean Color which prints output colored if turned on. Every Receiver has also its own log format.
Initilization
First you have to install the package.
go get -u github.com/mbndr/logo
After that you can import it.
import "github.com/mbndr/logo"
Simple
It's possible to create a simple logger with a io.Writer, the log level and a color boolean as parameter.
// Create a simple cli logger with activated colors which logs everything
log := logo.NewSimpleLogger(os.Stderr, logo.DEBUG, "prefix ", true)
Advanced
You can create multiple Receivers and add it to a new Logger.
// Receiver for the terminal which logs everything
cliRec := logo.NewReceiver(os.Stderr, "prefix ")
cliRec.Color = true
cliRec.Level = logo.DEBUG
// Helper function to get a os.File with the correct options
logFile, _ := logo.Open("./example/logo.log")
// Receiver for the log file
// This will log with level INFO (default) and have no colors activated
// Also the log format is simpler (f.e. ERRO: Message)
fileRec := logo.NewReceiver(logFile, "prefix ")
fileRec.Format = "%s: %s"
// Create the logger
log := logo.NewLogger(cliRec, fileRec)
Usage
If you created you logo.Logger object, there are a few methods you can use to log.
// Methods which write like log.Println()
log.Debug("First debug", " and another string to log")
log.Info("Information")
log.Warn("Warning", " message")
log.Error("Error message")
log.Fatal("Fatal error", " because of something")
// Methods which write like log.Printf()
log.Debugf("Debug value %d", 16)
log.Infof("Listening on port %d", 8080)
log.Warnf("Invalid user %s", user.Name)
log.Errorf("Couldn't load config file: %s", path)
log.Fatalf("Fatal error: %s", err.Error())
// Disable the logger
log.Active = false
Tests
There are a few unit tests written for this library. To run them cd into the project directory and run this.
go test -v
*Note that all licence references and agreements mentioned in the logo README section above
are relevant to that project's source code only.