2013-10-16 23:27:10 +04:00
|
|
|
# Logrus
|
|
|
|
|
2014-03-11 03:22:08 +04:00
|
|
|
Logrus is a simple, opinionated structured logging package for Go which is
|
|
|
|
completely API compatible with the standard library logger.
|
2013-10-16 23:27:10 +04:00
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
#### Fields
|
2013-10-16 23:27:10 +04:00
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
Logrus encourages careful, informative logging. It encourages the use of logging
|
2014-03-07 06:26:05 +04:00
|
|
|
fields instead of long, unparseable error messages. For example, instead of:
|
2014-03-07 06:20:13 +04:00
|
|
|
`log.Fatalf("Failed to send event %s to topic %s with key %d")`, you should log
|
|
|
|
the much more discoverable:
|
2013-10-16 23:27:10 +04:00
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
```go
|
|
|
|
log = logrus.New()
|
|
|
|
log.WithFields(&logrus.Fields{
|
|
|
|
"event": event,
|
|
|
|
"topic": topic,
|
|
|
|
"key": key
|
|
|
|
}).Fatal("Failed to send event")
|
|
|
|
```
|
|
|
|
|
|
|
|
We've found this API forces you to think about logging in a way that produces
|
|
|
|
much more useful logging messages. The `WithFields` call is optional.
|
|
|
|
|
2014-03-07 06:26:05 +04:00
|
|
|
In general, with Logrus using any of the `printf`-family functions should be
|
|
|
|
seen as a hint you want to add a field, however, you can still use the
|
|
|
|
`printf`-family functions with Logrus.
|
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
#### Hooks
|
2013-10-16 23:27:10 +04:00
|
|
|
|
2014-03-07 06:26:05 +04:00
|
|
|
You can add hooks for logging levels. For example to send errors to an exception
|
|
|
|
tracking service:
|
2013-10-16 23:27:10 +04:00
|
|
|
|
|
|
|
```go
|
2014-03-07 06:20:13 +04:00
|
|
|
log.AddHook("error", func(entry logrus.Entry) {
|
|
|
|
err := airbrake.Notify(errors.New(entry.String()))
|
|
|
|
if err != nil {
|
|
|
|
log.WithFields(logrus.Fields{
|
|
|
|
"source": "airbrake",
|
|
|
|
"endpoint": airbrake.Endpoint,
|
|
|
|
}).Info("Failed to send error to Airbrake")
|
|
|
|
}
|
|
|
|
})
|
|
|
|
```
|
|
|
|
|
|
|
|
#### Level logging
|
2013-10-16 23:27:10 +04:00
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
Logrus has six levels: Debug, Info, Warning, Error, Fatal and Panic.
|
2013-10-16 23:27:10 +04:00
|
|
|
|
2014-02-24 05:19:34 +04:00
|
|
|
```go
|
2014-03-07 06:49:10 +04:00
|
|
|
log.Debug("Useful debugging information.")
|
2014-03-07 06:20:13 +04:00
|
|
|
log.Info("Something noteworthy happened!")
|
|
|
|
log.Warn("You should probably take a look at this.")
|
|
|
|
log.Error("Something failed but I'm not quitting.")
|
|
|
|
log.Fatal("Bye.")
|
|
|
|
log.Panic("I'm bailing.")
|
|
|
|
```
|
|
|
|
|
2014-03-07 06:49:10 +04:00
|
|
|
You can set the logging level:
|
|
|
|
|
|
|
|
```go
|
|
|
|
// Will log anything that is info or above, default.
|
|
|
|
logrus.Level = LevelInfo
|
|
|
|
```
|
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
#### Entries
|
|
|
|
|
|
|
|
Besides the fields added with `WithField` or `WithFields` some fields are
|
|
|
|
automatically added to all logging events:
|
|
|
|
|
|
|
|
1. `time`. The timestamp when the entry was created.
|
|
|
|
2. `msg`. The logging message passed to `{Info,Warn,Error,Fatal,Panic}` after
|
|
|
|
the `AddFields` call. E.g. `Failed to send event.`
|
|
|
|
3. `level`. The logging level. E.g. `info`.
|
|
|
|
4. `file`. The file (and line) where the logging entry was created. E.g.,
|
|
|
|
`main.go:82`.
|
|
|
|
|
|
|
|
#### Environments
|
|
|
|
|
|
|
|
Logrus has no notion of environment. If you wish for hooks and formatters to
|
|
|
|
only be used in specific environments, you should handle that yourself. For
|
|
|
|
example, if your application has a global variable `Environment`, which is a
|
|
|
|
string representation of the environment you could do:
|
|
|
|
|
|
|
|
```go
|
|
|
|
init() {
|
|
|
|
// do something here to set environment depending on an environment variable
|
|
|
|
// or command-line flag
|
|
|
|
|
|
|
|
if Environment == "production" {
|
|
|
|
log.SetFormatter(logrus.JSONFormatter)
|
|
|
|
} else {
|
|
|
|
// The TextFormatter is default, you don't actually have to do this.
|
|
|
|
log.SetFormatter(logrus.TextFormatter)
|
|
|
|
}
|
2013-10-16 23:27:10 +04:00
|
|
|
}
|
|
|
|
```
|
2014-02-24 05:19:34 +04:00
|
|
|
|
2014-03-07 06:20:13 +04:00
|
|
|
#### Formats
|
|
|
|
|
|
|
|
The built in logging formatters are:
|
|
|
|
|
|
|
|
* `logrus.TextFormatter`. Logs the event in colors if stdout is a tty, otherwise
|
2014-03-07 21:51:29 +04:00
|
|
|
without colors.
|
|
|
|
* `logrus.JSONFormatter`. Logs fields as JSON.
|
2014-03-07 06:20:13 +04:00
|
|
|
|
|
|
|
You can define your formatter taking an entry. `entry.Data` is a `Fields` type
|
|
|
|
which is a `map[string]interface{}` with all your fields as well as the default
|
|
|
|
ones (see Entries above):
|
|
|
|
|
|
|
|
```go
|
|
|
|
log.SetFormatter(func(entry *logrus.Entry) {
|
|
|
|
serialized, err = json.Marshal(entry.Data)
|
|
|
|
if err != nil {
|
|
|
|
return nil, log.WithFields(&logrus.Fields{
|
|
|
|
"source": "log formatter",
|
|
|
|
"entry": entry.Data
|
|
|
|
}).AsError("Failed to serialize log entry to JSON")
|
|
|
|
}
|
|
|
|
})
|
|
|
|
```
|