Logrus - Structured, pluggable logging for Go.

  •        58

Logrus is a structured logger for Go (golang), completely API compatible with the standard library logger. There is a support to add hooks for logging levels. For example to send errors to an exception tracking service on Error, Fatal and Panic, info to StatsD or log to multiple places simultaneously, e.g. syslog.




Related Projects

lg - Context logger backed by Logrus, including a structured HTTP RequestLogger

The lg ("log") package is a context-based application logger built on the Logrus package (https://github.com/sirupsen/logrus). It also includes a HTTP request logging middleware, lg.RequestLogger.See the example for a sample program.

log - Structured logging package for Go.

Package log implements a simple structured logging API inspired by Logrus, designed with centralization in mind. Read more on Medium.

gournal - Gournal (pronounced "Journal") is a Context-aware logging facade for Go.

Gournal (pronounced "Journal") is a Context-aware logging framework that introduces the Google Context type as a first-class parameter to all common log functions such as Info, Debug, etc.Instead of being Yet Another Go Log library, Gournal actually takes its inspiration from the Simple Logging Facade for Java (SLF4J). Gournal is not attempting to replace anyone's favorite logger, rather existing logging frameworks such as Logrus, Zap, etc. can easily participate as a Gournal Appender.

logberry - A structured logging package for Go services & applications.

Most log output libraries fall into one of two camps: * Super simple, with a global API that's really easy to use but has no structure beyond a component label and message level or type; * More complex, but focused on extensive formatting controls and/or various output serializers, pipes, aggregators, and managers.Logberry is a bit different, and places more focus on *what* you'relogging, rather than *how*. At the core, its log events are basedaround key/value pairs rather than arbitrary st

logxi - A 12-factor app logger built for performance and happy development

log XI is a structured 12-factor app logger built for speed and happy development.A logger should be efficient and minimize performance tax. logxi encodes JSON 2X faster than logrus and log15 with primitive types. When diagnosing a problem in production, troubleshooting often means enabling small trace data in Debug and Info statements for some period of time.

Algernon - Pure Go web server with built-in Lua, Markdown, HyperApp and Pongo2 support

Web server with built-in support for HTTP/2, Lua, Markdown, Pongo2, HyperApp, Amber, Sass(SCSS), GCSS, JSX, BoltDB, Redis, PostgreSQL, MariaDB/MySQL, rate limiting, graceful shutdown, plugins, users and permissions. Uses no external libraries, only pure Go.

zerolog - Zero Allocation JSON Logger

The zerolog package provides a fast and simple logger dedicated to JSON output.Zerolog's API is designed to provide both a great developer experience and stunning performance. Its unique chaining API allows zerolog to write JSON log events by avoiding allocations and reflection.

glogrus - Logrus logging for Goji

glogrus provides structured logging via logrus for Goji.slog and lunk looks interesting.

logger - Minimalistic logging library for Go.

Minimalistic logging library for Go.It gives only three methods; Info, Timer and Error.

log - :green_book: Simple, configurable and scalable Structured Logging for Go.

There's allot of great stuff out there, but also thought a log library could be made easier to use, more efficient by reusing objects and more performant using channels.DebugLevel - Info useful to developers for debugging the application, not useful during operations.

log15 - Structured, composable logging for Go

Package log15 provides an opinionated, simple toolkit for best-practice logging in Go (golang) that is both human and machine readable. It is modeled after the Go standard library's io and net/http packages and is an alternative to the standard library's log package.The API of the master branch of log15 should always be considered unstable. If you want to rely on a stable API, you must vendor the library.

mlog - A simple logging module for go, with a rotating file feature and console logging.

A simple logging module for go, with a rotating file feature and console logging.By default, the log will be rolled over to a backup file when its size reaches 10Mb and 10 such files will be created (and eventually reused).

seelog - Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting

Seelog is a powerful and easy-to-learn logging framework that provides functionality for flexible dispatching, filtering, and formatting log messages. It is natively written in the Go programming language.

log - Logging packages for Go

You are more than welcome to ask questions on the Go mailing-list and open issues here if you find bugs.Package stdlog provides simple and fast logging to the standard output (stdout) and is optimized for programs launched via a shell or cron. It can also be used to log to a file by redirecting the standard output to a file. This package is thread-safe.

zap - Blazing fast, structured, leveled logging in Go.

Blazing fast, structured, leveled logging in Go.Note that zap only supports the two most recent minor versions of Go.

logger - Cross platform Go logging library.

Logger is a simple cross platform Go logging library for Windows, Linux, and macOS, it can log to the Windows event log, Linux/macOS syslog, and an io.Writer.This is not an official Google product.

journalhook - Logrus plugin for logging to systemd-journald

Note that this will discard all journal output. Generally when logging to the journal, your application will be managed by systemd, which will automatically capture command output and send it to the journal. This way we preempt that potential log message duplication.

tinylog - tinylog is a lightweight logging framework for Java and Android.

tinylog is a lightweight open-source logging framework for Java and Android, optimized for ease of use. The logger of tinylog is static, so it isn't necessary to create an instance of the logger before logging. By default all log entries of the level info or higher are written to the console.