Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Ruby GELF library (Graylog2 Extended Log Format). Download the Gem via Gemcutter. (

Merge pull request #27 from mrnugget/make_compatible_to_ruby_logger

Make GELF::Logger#add compatible with Logger#add
latest commit 6b12be4576
Jochen Schalanda joschi authored



This is the new GELF gem written by Alexey Palazhchenko. It is based on the old gem by Lennart Koopmann and allows you to send GELF messages to Graylog2 server instances. See for more information about GELF and for API documentation.

Works with Ruby 1.8.7, 1.9.x. and 2.0.x.




This allows you to sent arbitary messages via UDP to your Graylog2 server.

n ="localhost", 12201)

# Send with custom attributes and an additional parameter "foo"
n.notify!(:short_message => "foo", :full_message => "something here\n\nbacktrace?!", :_foo => "bar")

# Pass any object that responds to .to_hash


The Gelf::Logger is compatible with the standard Ruby Logger interface and can be used interchangeably. Under the hood it uses Gelf::Notifier to send log messages via UDP to Graylog2.

logger ="localhost", 12201, "WAN", { :facility => "appname" })

logger.debug "foobar" "foobar"
logger.warn "foobar"
logger.error "foobar"
logger.fatal "foobar"

logger << "foobar"

Since it's compatible with the Logger interface, you can also use it in your Rails application:

# config/environments/production.rb
config.logger ="localhost", 12201, "WAN", { :facility => "appname" })

Note on Patches/Pull Requests

  • Fork the project.

  • Make your feature addition or bug fix.

  • Add tests for it. This is important so I don't break it in a future version unintentionally.

  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)

  • Send me a pull request. Bonus points for topic branches.


Copyright © 2010-2013 Lennart Koopmann and Alexey Palazhchenko. See LICENSE for details.

Something went wrong with that request. Please try again.