Skip to content
Leveled execution logs for Go (fork of
Branch: master
Clone or download
#79 Compare This branch is 117 commits ahead of golang:master.
k8s-ci-robot Merge pull request #20 from munnerz/logr
Add SetLogger function to intercept klog output with logr
Latest commit cd60aa4 Aug 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add common PR/Issues templates Nov 14, 2018
examples fix golint error Jan 25, 2019
integration_tests Backfill integration tests for selecting log destinations Aug 1, 2019
klogr Merge pull request #20 from munnerz/logr Aug 14, 2019
.travis.yml Test with golang 1.12.x Aug 5, 2019 Add the code of conduct Dec 27, 2018
LICENSE Initial commit Jul 16, 2013
OWNERS Bootstrapping a team to take care of klog Feb 13, 2019 fix broken links Jul 19, 2019 Add OWNERS and other template files (#12) Nov 2, 2018
SECURITY_CONTACTS Update embargo doc link in SECURITY_OWNERS and changes PST to PSC Mar 8, 2019 Add the code of conduct Dec 27, 2018
go.sum Add go modules files Jul 9, 2019
klog.go Merge pull request #20 from munnerz/logr Aug 14, 2019
klog_file.go Add a log-file-max-size flag to fix large logfile (>1.8GB) truncation. Apr 11, 2019
klog_test.go Merge pull request #20 from munnerz/logr Aug 14, 2019


klog is a permanent fork of

Why was klog created?

The decision to create klog was one that wasn't made lightly, but it was necessary due to some drawbacks that are present in glog. Ultimately, the fork was created due to glog not being under active development; this can be seen in the glog README:

The code in this repo [...] is not itself under development

This makes us unable to solve many use cases without a fork. The factors that contributed to needing feature development are listed below:

  • glog presents a lot "gotchas" and introduces challenges in containerized environments, all of which aren't well documented.
  • glog doesn't provide an easy way to test logs, which detracts from the stability of software using it
  • A long term goal is to implement a logging interface that allows us to add context, change output format, etc.

Historical context is available here:

How to use klog

  • Replace imports for with
  • Use klog.InitFlags(nil) explicitly for initializing global flags as we no longer use init() method to register the flags
  • You can now use log-file instead of log-dir for logging to a single file (See examples/log_file/usage_log_file.go)
  • If you want to redirect everything logged using klog somewhere else (say syslog!), you can use klog.SetOutput() method and supply a io.Writer. (See examples/set_output/usage_set_output.go)
  • For more logging conventions (See Logging Conventions)

Coexisting with glog

This package can be used side by side with glog. This example shows how to initialize and syncronize flags from the global flag.CommandLine FlagSet. In addition, the example makes use of stderr as combined output by setting alsologtostderr (or logtostderr) to true.

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

You can reach the maintainers of this project at:

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.


Leveled execution logs for Go.

This is an efficient pure Go implementation of leveled logs in the manner of the open source C++ package

By binding methods to booleans it is possible to use the log package without paying the expense of evaluating the arguments to the log. Through the -vmodule flag, the package also provides fine-grained control over logging at the file level.

The comment from glog.go introduces the ideas:

Package glog implements logging analogous to the Google-internal
C++ INFO/ERROR/V setup.  It provides functions Info, Warning,
Error, Fatal, plus formatting variants such as Infof. It
also provides V-style logging controlled by the -v and
-vmodule=file=2 flags.

Basic examples:

	glog.Info("Prepare to repel boarders")

	glog.Fatalf("Initialization failed: %s", err)

See the documentation for the V function for an explanation
of these examples:

	if glog.V(2) {
		glog.Info("Starting transaction...")

	glog.V(2).Infoln("Processed", nItems, "elements")

The repository contains an open source version of the log package used inside Google. The master copy of the source lives inside Google, not here. The code in this repo is for export only and is not itself under development. Feature requests will be ignored.

Send bug reports to

You can’t perform that action at this time.