logrus/README.md

163 lines
4.7 KiB
Markdown
Raw Normal View History

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-11 03:59:18 +04:00
Nicely color-coded in development (when a TTY is attached):
[Imgur](http://i.imgur.com/PY7qMwd.png)
With `log.Formatter = new(logrus.JSONFormatter)`:
```json
{"animal":"walrus","level":"info","msg":"A group of walrus emerges from the
ocean","size":"10","time":"2014-03-10 19:57:38.562264131 -0400 EDT"}
{"level":"warning","msg":"The group's number increased
tremendously!","number":122,"omg":true,"time":"2014-03-10 19:57:38.562471297
-0400 EDT"}
{"animal":"walrus","level":"info","msg":"A giant walrus
appears!","size":"10","time":"2014-03-10 19:57:38.562500591 -0400 EDT"}
{"animal":"walrus","level":"info","msg":"Tremendously sized cow enters the
ocean.","size":"9","time":"2014-03-10 19:57:38.562527896 -0400 EDT"}
{"level":"fatal","msg":"The ice
breaks!","number":100,"omg":true,"time":"2014-03-10 19:57:38.562543128 -0400
EDT"}
```
2014-03-07 06:20:13 +04:00
#### Fields
2013-10-16 23:27:10 +04:00
2014-03-11 03:30:06 +04:00
Logrus encourages careful, structured 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()
2014-03-11 03:27:19 +04:00
2014-03-07 06:20:13 +04:00
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
2014-03-11 03:52:39 +04:00
tracking service on `Error`, `Fatal` and `Panic`.
2013-10-16 23:27:10 +04:00
```go
2014-03-11 03:27:19 +04:00
log = logrus.New()
type AirbrakeHook struct {}
2014-03-11 03:30:06 +04:00
// `Fire()` takes the entry that the hook is fired for. `entry.Data[]` contains
// the fields for the entry. See the Fields section of the README.
2014-03-11 03:27:19 +04:00
func (hook *AirbrakeHook) Fire(entry *Entry) (error) {
2014-03-07 06:20:13 +04:00
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")
}
2014-03-11 03:27:19 +04:00
return nil
}
2014-03-11 03:52:39 +04:00
// `Levels()` returns a slice of `Levels` the hook is fired for.
func (hook *AirbrakeHook) Levels() []logrus.Level {
return []logrus.Level{
logrus.Error,
logrus.Fatal,
logrus.Panic
2014-03-11 03:27:19 +04:00
}
}
2014-03-07 06:20:13 +04:00
```
#### 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.
2014-03-11 03:52:39 +04:00
log.Level = logrus.Info
2014-03-07 06:49:10 +04:00
```
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`.
#### 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
2014-03-11 03:27:19 +04:00
log := logrus.New()
2014-03-07 06:20:13 +04:00
if Environment == "production" {
2014-03-11 03:27:19 +04:00
log.Formatter = new(logrus.JSONFormatter)
2014-03-07 06:20:13 +04:00
} else {
// The TextFormatter is default, you don't actually have to do this.
2014-03-11 03:27:19 +04:00
log.Formatter = new(logrus.TextFormatter)
2014-03-07 06:20:13 +04:00
}
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
2014-03-11 03:27:19 +04:00
type MyJSONFormatter struct {
}
log.Formatter = new(MyJSONFormatter)
func (f *JSONFormatter) Format(entry *Entry) ([]byte, error) {
serialized, err := json.Marshal(entry.Data)
if err != nil {
return nil, fmt.Errorf("Failed to marshal fields to JSON, %v", err)
}
return append(serialized, '\n'), nil
}
2014-03-07 06:20:13 +04:00
```