go-kit/log sits at 194 stars on GitHub, written primarily in Go. A minimal and extensible structured logger
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
package log provides a minimal interface for structured logging in services.
It may be wrapped to encode conventions, enforce type-safety, provide leveled
logging, and so on. It can be used for both typical application log events,
and log-structured data streams.
Structured logging
Structured logging is, basically, conceding to the reality that logs are
data, and warrant some level of schematic rigor. Using a stricter,
key/value-oriented message format for our logs, containing contextual and
semantic information, makes it much easier to get insight into the
operational activity of the systems we build. Consequently, package log is
of the strong belief that structured logging offers great benefits in exchange
for minimal effort.
Migrating from unstructured to structured logging is probably a lot easier
than you'd expect.
// Unstructured
log.Printf("HTTP server listening on %s", addr)
// Structured
logger.Log("transport", "HTTP", "addr", addr, "msg", "listening")
Usage
Typical application logging
w := log.NewSyncWriter(os.Stderr)
logger := log.NewLogfmtLogger(w)
logger.Log("question", "what is the meaning of life?", "answer", 42)
// Output:
// question="what is the meaning of life?" answer=42
package log is centered on the one-method Logger interface.
type Logger interface {
Log(keyvals ...interface{}) error
}
This interface, and its supporting code like is the product of much iteration
and evaluation. For more details on the evolution of the Logger interface,
see The Hunt for a Logger Interface,
a talk by Chris Hines.
Also, please see
#63,
#76,
#131,
#157,
#164, and
#252
to review historical conversations about package log and the Logger interface.
Value-add packages and suggestions,
like improvements to the leveled logger,
are of course welcome. Good proposals should
Be composable with contextual loggers,
Not break the behavior of log.Caller in any wrapped contextual loggers, and
Be friendly to packages that accept only an unadorned log.Logger.
Benchmarks & comparisons
There are a few Go logging benchmarks and comparisons that include Go kit's package log.
imkira/go-loggers-bench includes kit/log
uber-common/zap, a zero-alloc logging library, includes a comparison with kit/log
Yes — go-kit/log ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/go-kit/log.
What is go-kit/log?
go-kit/log (go-kit/log) is a Go project on GitHub. From the project's own README: A minimal and extensible structured logger
Where do I read more about go-kit/log?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/go-kit/log is the definitive source.
Read full README in the tab above.
Want a second opinion on log?
Ask an AI that can read this page — one click and you get its take on log.