No description or website provided.
Latest commit fd709b1 Jan 5, 2016 @freeformz Merge pull request #47 from freeformz/update_for_deprecated_timeouterror
TimeoutError is deprecated, use Timeout::Error instead
Failed to load latest commit information.
spec Update spec to handle when the log device is Syslog, and when it is, … Dec 8, 2015
.gitignore fixups Jun 17, 2011
.travis.yml TimeoutError is deprecated, use Timeout::Error instead Jan 5, 2016
Gemfile Travis updates Dec 14, 2015
LICENSE add a license Mar 4, 2011 Added details about UDP Jun 3, 2015
Rakefile initial commit Feb 26, 2011
logglier.gemspec Oops. Too old of a version matched. May 13, 2015


Build Status

Send logged messages to Loggly using either the HTTP API or Syslog/UDP. Check out Loggly's Ruby logging documentation to learn more.

Can be used in place of Ruby's Logger (

In fact, it (currently) returns an instance of Logger.


require 'logglier'

log =<INPUT URL>)"hello from logglier")

With Rails


RailsApplication::Application.configure do
  config.logger =<INPUT URL>)

With Rails 4


loggly ='[your-customer-token]/tag/rails', threaded: true, format: :json)

^ Submitted by:

Input URLs

HTTP Inputs'[your-customer-token]')

The id is provided by loggly, look at the input's details page To make sure the http client doesn't block too long read_timeout and open_timeout are set to 2 seconds by default. This can be overridden like so:'[your-customer-token]',
             :read_timeout => <#>,
             :open_timeout => <#> )

Threaded Delivery

Creating a new Logglier instance, pointed at a http input, with the :threaded => true option will tell Logglier to deliver log messages for that logger in a seperate thread. Each new Logglier instance gets it's own delivery thread and those threads are joined at exit to ensure log message delivery.

             :threaded => true)

JSON Formatting

add the ':format => :json' when creating a new Logglier instance. Make sure to use a HTTP input that has JSON enabled. Can also be used with threaded delivery.

             :format => :json)

Logglier uses MultiJson to delegate the choice of JSON libraries to you, but I recommend using Yajl, just require the json gem of your choice before logglier.

Syslog TCP/UDP Inputs'[udp|tcp]://<hostname>:<port>/<facility>')

The facility is optional and defaults to 16 (local0) if none is specified. Facilities are just integers from 0 to 23, see

Logging returns a ruby Logger object, so take a look at:

The Logger's logdev has some special format handling though.

Logging a string

log.warn "test"

Will produce the following log message in Loggly:

"<Date> severity=WARN, test"

Logging a Hash

log.warn :boom => :box, :bar => :soap

Will produce the following log message in Loggly:

"<Date> severity=WARN, boom=box, bar=soap"

Logging Fast

If speed is a concern, then you should pick a fast transport protocol. Here is their speed ranking from fastest to slowest:

  1. Syslog UDP
  2. Syslog TCP
  3. Threaded HTTP
  4. Threaded HTTPS
  5. Blocking HTTP
  6. Blocking HTTPS

Syslog is the fastest because it's the most efficient protocol and the syslog daemon runs asynchronously with it's own queuing system (and optionally TLS encryption).

UDP uses a simple connectionless transmission model with a minimum of protocol mechanism. There is no guarantee of delivery, ordering, or duplicate protection.

Threaded won't block your app but it can use up more memory and stack space. Blocking is the slowest because your app will wait for the data to be received by Loggly.

HTTPS is slower than HTTP because it requires an extra round trip to setup the secure connection.


Pull requests welcome


  • Support ActiveSupport Notifications for newer rails
  • Alternative https implementations (Typheous, Excon, etc). May be faster?
  • EM Integration?