Security News
Weekly Downloads Now Available in npm Package Search Results
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
gitee.com/menciis/logx
logx is a zero-dependency simple, fast and easy-to-use level-based logger written in Go Programming Language.
The only requirement is the Go Programming Language*.
$ go get gitee.com/menciis/logx@latest
Or edit your project's go.mod file and execute $ go build.
module your_project_name
go 1.19
require (
gitee.com/menciis/logx v0.1.8
)
$ go build
$ go get gitee.com/menciis/logx@latest
package main
import (
"gitee.com/menciis/logx"
)
func main() {
// Default Output is `os.Stdout`,
// but you can change it:
// logx.SetOutput(os.Stderr)
// Time Format defaults to: "2006/01/02 15:04"
// you can change it to something else or disable it with:
// logx.SetTimeFormat("")
// Level defaults to "info",
// but you can change it:
logx.SetLevel("debug")
logx.Println("This is a raw message, no levels, no colors.")
logx.Info("This is an info message, with colors (if the output is terminal)")
logx.Warn("This is a warning message")
logx.Error("This is an error message")
logx.Debug("This is a debug message")
logx.Fatal(`Fatal will exit no matter what,
but it will also print the log message if logger's Level is >=FatalLevel`)
}
Name | Method | Text | Color |
---|---|---|---|
"fatal" | Fatal, Fatalf | [FTAL] | Red background |
"error" | Error, Errorf | [ERRO] | Red foreground |
"warn" | Warn, Warnf, Warningf | [WARN] | Magenta foreground |
"info" | Info, Infof | [INFO] | Cyan foreground |
"debug" | Debug, Debugf | [DBUG] | Yellow foreground |
On debug level the logger will store stacktrace information to the log instance, which is not printed but can be accessed through a
Handler
(see below).
// GetTextForLevel returns the level's (rich) text.
fatalRichText := logx.GetTextForLevel(logx.FatalLevel, true)
// fatalRichText == "\x1b[41m[FTAL]\x1b[0m"
// ParseLevel returns a Level based on its string name.
level := logx.ParseLevel("debug")
// level == logx.DebugLevel
You can customize the log level attributes.
func init() {
// Levels contains a map of the log levels and their attributes.
errorAttrs := logx.Levels[logx.ErrorLevel]
// Change a log level's text.
customColorCode := 156
errorAttrs.SetText("custom text", customColorCode)
// Get (rich) text per log level.
enableColors := true
errorRichText := errorAttrs.Text(enableColors)
}
Alternatively, to change a specific text on a known log level, you can just call:
logx.ErrorText("custom text", 156)
The logx.Logger
is using common, expected log methods, therefore you can integrate it with ease.
Take for example the badger database. You want to add a prefix of [badger]
in your logs when badger wants to print something.
Child
function,opts := badger.DefaultOptions("./data")
opts.Logger = logx.Child("[badger]").DisableNewLine()
db, err := badger.Open(opts)
// [...]
You can put logx
in front of your existing loggers using the Install and InstallStd methods.
Any level-based Logger that implements the ExternalLogger can be adapted.
E.g. sirupsen/logrus:
// Simulate a logrus logger preparation.
logrus.SetLevel(logrus.InfoLevel)
logrus.SetFormatter(&logrus.JSONFormatter{})
logx.Install(logrus.StandardLogger())
logx.Debug(`this debug message will not be shown,
because the logrus level is InfoLevel`)
logx.Error(`this error message will be visible as JSON,
because of logrus.JSONFormatter`)
Any standard logger (without level capabilities) that implements the StdLogger can be adapted using the InstallStd method.
E.g. log
standard package:
// Simulate a log.Logger preparation.
myLogger := log.New(os.Stdout, "", 0)
logx.SetLevel("error")
logx.InstallStd(myLogger)
logx.Error("error message")
Any value that completes the Formatter interface can be used to write to the (leveled) output writer. By default the "json"
formatter is available.
import "gitee.com/menciis/logx"
func main() {
logx.SetLevel("debug")
logx.SetFormat("json", " ") // < --
// main.go#29
logx.Debugf("This is a %s with data (debug prints the stacktrace too)", "message", logx.Fields{
"username": "kataras",
})
}
Output
{
"timestamp": 1591423477,
"level": "debug",
"message": "This is a message with data (debug prints the stacktrace too)",
"fields": {
"username": "kataras"
},
"stacktrace": [
{
"function": "main.main",
"source": "C:/example/main.go:29"
}
]
}
logx.RegisterFormatter(new(myFormatter))
logx.SetFormat("myformat", options...)
The Formatter
interface looks like this:
// Formatter is responsible to print a log to the logger's writer.
type Formatter interface {
// The name of the formatter.
String() string
// Set any options and return a clone,
// generic. See `Logger.SetFormat`.
Options(opts ...interface{}) Formatter
// Writes the "log" to "dest" logger.
Format(dest io.Writer, log *Log) bool
}
Handler
The Logger can accept functions to handle (and print) each Log through its Handle method. The Handle method accepts a Handler.
type Handler func(value *Log) (handled bool)
This method can be used to alter Log's fields based on custom logic or to change the output destination and its output format.
Create a JSON handler
import "encoding/json"
func jsonOutput(l *logx.Log) bool {
enc := json.NewEncoder(l.Logger.GetLevelOutput(l.Level.String()))
enc.SetIndent("", " ")
err := enc.Encode(l)
return err == nil
}
Register the handler and log something
import "gitee.com/menciis/logx"
func main() {
logx.SetLevel("debug")
logx.Handle(jsonOutput)
// main.go#29
logx.Debugf("This is a %s with data (debug prints the stacktrace too)", "message", logx.Fields{
"username": "kataras",
})
}
test | times ran (large is better) | ns/op (small is better) | B/op (small is better) | allocs/op (small is better) |
---|---|---|---|---|
BenchmarklogxPrint | 10000000 | 3749 ns/op | 890 B/op | 28 allocs/op |
BenchmarkLogrusPrint | 3000000 | 9609 ns/op | 1611 B/op | 64 allocs/op |
Click here for details.
If you find that something is not working as expected please open an issue.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.