package log
Import Path
log (on golang.org and go.dev)
Dependency Relation
imports 6 packages, and imported by 7 packages
Involved Source Files
d-> log.go
Exported Type Names
Exported Values
func
Fatal(v ...interface{})
Fatal is equivalent to Print() followed by a call to os.Exit(1).
func
Fatalf(format
string, v ...interface{})
Fatalf is equivalent to Printf() followed by a call to os.Exit(1).
func
Fatalln(v ...interface{})
Fatalln is equivalent to Println() followed by a call to os.Exit(1).
func
Flags()
int
Flags returns the output flags for the standard logger.
The flag bits are Ldate, Ltime, and so on.
const
Ldate = 1 // the date in the local time zone: 2009/01/23
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
Llongfile = 8 // full file name and line number: /a/b/c/d.go:23
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
Lmicroseconds = 4 // microsecond resolution: 01:23:23.123123. assumes Ltime.
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
Lmsgprefix = 64 // move the "prefix" from the beginning of the line to before the message
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
Lshortfile = 16 // final file name element and line number: d.go:23. overrides Llongfile
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
LstdFlags = 3 // initial values for the standard logger
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
Ltime = 2 // the time in the local time zone: 01:23:23
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
const
LUTC = 32 // if Ldate or Ltime is set, use UTC rather than the local time zone
These flags define which text to prefix to each log entry generated by the Logger.
Bits are or'ed together to control what's printed.
With the exception of the Lmsgprefix flag, there is no
control over the order they appear (the order listed here)
or the format they present (as described in the comments).
The prefix is followed by a colon only when Llongfile or Lshortfile
is specified.
For example, flags Ldate | Ltime (or LstdFlags) produce,
2009/01/23 01:23:23 message
while flags Ldate | Ltime | Lmicroseconds | Llongfile produce,
2009/01/23 01:23:23.123123 /a/b/c/d.go:23: message
func
New(out
io.
Writer, prefix
string, flag
int) *
Logger
New creates a new Logger. The out variable sets the
destination to which log data will be written.
The prefix appears at the beginning of each generated log line, or
after the log header if the Lmsgprefix flag is provided.
The flag argument defines the logging properties.
func
Output(calldepth
int, s
string)
error
Output writes the output for a logging event. The string s contains
the text to print after the prefix specified by the flags of the
Logger. A newline is appended if the last character of s is not
already a newline. Calldepth is the count of the number of
frames to skip when computing the file name and line number
if Llongfile or Lshortfile is set; a value of 1 will print the details
for the caller of Output.
func
Panic(v ...interface{})
Panic is equivalent to Print() followed by a call to panic().
func
Panicf(format
string, v ...interface{})
Panicf is equivalent to Printf() followed by a call to panic().
func
Panicln(v ...interface{})
Panicln is equivalent to Println() followed by a call to panic().
func
Prefix()
string
Prefix returns the output prefix for the standard logger.
func
Print(v ...interface{})
Print calls Output to print to the standard logger.
Arguments are handled in the manner of fmt.Print.
func
Printf(format
string, v ...interface{})
Printf calls Output to print to the standard logger.
Arguments are handled in the manner of fmt.Printf.
func
Println(v ...interface{})
Println calls Output to print to the standard logger.
Arguments are handled in the manner of fmt.Println.
func
SetFlags(flag
int)
SetFlags sets the output flags for the standard logger.
The flag bits are Ldate, Ltime, and so on.
func
SetOutput(w
io.
Writer)
SetOutput sets the output destination for the standard logger.
func
SetPrefix(prefix
string)
SetPrefix sets the output prefix for the standard logger.
func
Writer()
io.
Writer
Writer returns the output destination for the standard logger.
