README.md in lograge-0.1.2 vs README.md in lograge-0.2.0

- old
+ new

@@ -50,20 +50,20 @@ gem "lograge" ``` Enable it for the relevant environments, e.g. production: -``` +```ruby # config/environments/production.rb MyApp::Application.configure do config.lograge.enabled = true end ``` You can also add a hook for own custom data -``` +```ruby # config/environments/staging.rb MyApp::Application.configure do config.lograge.enabled = true # custom_options can be a lambda or hash @@ -77,11 +77,11 @@ Lograge supports multiple output formats. The most common is the default lograge format described above. Alternatively, you can also generate JSON logs in the json_event format used by [Logstash](http://logstash.net/). -``` +```ruby # config/environments/production.rb MyApp::Application.configure do config.lograge.log_format = :logstash end ``` @@ -159,9 +159,10 @@ contemplating, mainly because I want to find a good way to include them, a way that fits in with the general spirit of the log output generated by Lograge. **Changes** +* Add support for Graylog2 events (Lennart Koopmann, http://github.com/lennartkoopmann) * Add support for Logstash events (Holger Just, http://github.com/meineerde) * Fix for Rails 3.2.9 * Use keys everywhere (Curt Michols, http://github.com/asenchi) * Add `custom_options` to allow adding custom key-value pairs at runtime (Adam Cooper, https://github.com/adamcooper)