Version: v0.0.0-...-e215c4f Latest Latest

This package is not in the latest version of its module.

Go to latest
Published: Dec 31, 2019 License: Apache-2.0 Imports: 16 Imported by: 0



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")

Log output is buffered and written periodically using Flush. Programs should call Flush before exiting to guarantee all log output is written.

By default, all log statements write to files in a temporary directory. This package provides several flags that modify this behavior. As a result, flag.Parse must be called before any logging is done.

	Logs are written to standard error instead of to files.
	Logs are written to standard error as well as to files.
	Log events at or above this severity are logged to standard
	error as well as to files.
	Log files will be written to this directory instead of the
	default temporary directory.

Other flags provide aids to debugging.

	When set to a file and line number holding a logging statement,
	such as
	a stack trace will be written to the Info log whenever execution
	hits that statement. (Unlike with -vmodule, the ".go" must be
	Enable V-leveled logging at the specified level.
	The syntax of the argument is a comma-separated list of pattern=N,
	where pattern is a literal file name (minus the ".go" suffix) or
	"glob" pattern and N is a V level. For instance,
	sets the V level to 3 in all Go files whose names begin "gopher".



View Source
const (
	DEBUG = int(debugLog)
	INFO  = int(infoLog)
	WARN  = int(warningLog)
	ERROR = int(errorLog)
	FATAL = int(fatalLog)


View Source
var Stats struct {
	Debug, Info, Warning, Error OutputStats

Stats tracks the number of lines of output and number of bytes per severity level. Values must be read with atomic.LoadInt64.


func CloseIfNotNil

func CloseIfNotNil(c io.Closer)

log err if not nil

func FunIfNotNil

func FunIfNotNil(f func() error)

log err if not nil

func LogErrAndReturn

func LogErrAndReturn(err error) error

log err if not nil

func NewBaudLog

func NewBaudLog(dir, module, level string, toConsole bool) *baudLog

func Output

func Output(logging *loggingT, level int, depth int, format string, args ...interface{})

func ToInit

func ToInit(logging *loggingT)


type Level

type Level int32

Level specifies a level of verbosity for V logs. *Level implements flag.Value; the -v flag is of type Level and should be modified only through the flag.Value interface.

func (*Level) Get

func (l *Level) Get() interface{}

Get is part of the flag.Value interface.

func (*Level) Set

func (l *Level) Set(logging *loggingT, value string) error

Set is part of the flag.Value interface.

func (*Level) String

func (l *Level) String() string

String is part of the flag.Value interface.

type OutputStats

type OutputStats struct {
	// contains filtered or unexported fields

OutputStats tracks the number of output lines and bytes written.

func (*OutputStats) Bytes

func (s *OutputStats) Bytes() int64

Bytes returns the number of bytes written.

func (*OutputStats) Lines

func (s *OutputStats) Lines() int64

Lines returns the number of lines written.

type Verbose

type Verbose bool

Verbose is a boolean type that implements Infof (like Printf) etc. See the documentation of V for more information.

func V

func V(logging *loggingT, level Level) Verbose

V reports whether verbosity at the call site is at least the requested level. The returned value is a boolean of type Verbose, which implements Info, Infoln and Infof. These methods will write to the Info log if called. Thus, one may write either

if glog.V(2) { glog.Info("log this") }


glog.V(2).Info("log this")

The second form is shorter but the first is cheaper if logging is off because it does not evaluate its arguments.

Whether an individual call to V generates a log record depends on the setting of the -v and --vmodule flags; both are off by default. If the level in the call to V is at least the value of -v, or of -vmodule for the source file containing the call, the V call will log.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
t or T : Toggle theme light dark auto
y or Y : Canonical URL