Third party formatter to README.

This commit is contained in:
Antoine Grondin 2014-03-14 15:21:54 -04:00
parent 7d02fa59d7
commit 7e4ec7df6c
1 changed files with 6 additions and 2 deletions

View File

@ -138,7 +138,7 @@ automatically added to all logging events:
#### Environments #### Environments
Logrus has no notion of environment. Logrus has no notion of environment.
If you wish for hooks and formatters to only be used in specific environments, 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 you should handle that yourself. For example, if your application has a global
@ -166,12 +166,16 @@ Splunk or Logstash.
#### Formatters #### Formatters
The built logging formatters are: The built-in logging formatters are:
* `logrus.TextFormatter`. Logs the event in colors if stdout is a tty, otherwise * `logrus.TextFormatter`. Logs the event in colors if stdout is a tty, otherwise
without colors. without colors.
* `logrus.JSONFormatter`. Logs fields as JSON. * `logrus.JSONFormatter`. Logs fields as JSON.
Third party logging formatters:
* [`github.com/aybabtme/logzalgo.ZalgoFormatter`](https://github.com/aybabtme/logzalgo): invoking the P͉̫o̳̼̊w̖͈̰͎e̬͔̭͂r͚̼̹̲ ̫͓͉̳͈ō̠͕͖̚f̝͍̠ ͕̲̞͖͑Z̖̫̤̫ͪa͉̬͈̗l͖͎g̳̥o̰̥̅!̣͔̲̻͊̄ ̙̘̦̹̦.
You can define your formatter by implementing the `Formatter` interface, You can define your formatter by implementing the `Formatter` interface,
requiring a `Format` method. `Format` takes an `*Entry`. `entry.Data` is a requiring a `Format` method. `Format` takes an `*Entry`. `entry.Data` is a
`Fields` type (`map[string]interface{}`) with all your fields as well as the `Fields` type (`map[string]interface{}`) with all your fields as well as the