Alternate logger for Rails that emits syslog-style output. For use with pl_analyze gem.
Ruby
Latest commit b2c6ccc May 29, 2015 @topfunky Merge pull request #14 from jmonteiro/master
Remove duplicate rspec
Permalink
Failed to load latest commit information.
lib gemify Jun 20, 2013
spec gemify Jun 20, 2013
.rspec gemify Jun 20, 2013
Gemfile gemify Jun 20, 2013
Gemfile.lock gemify Jun 20, 2013
MIT-LICENSE.txt License (MIT) Apr 24, 2012
README.rdoc Update README.rdoc Dec 9, 2013
Rakefile Remove duplicate rspec May 28, 2015
hodel_3000_compliant_logger.gemspec Remove duplicate rspec May 28, 2015

README.rdoc

Hodel 3000 Compliant Logger

The Hodel 3000 Compliant Logger outputs like SyslogLogger (seattlerb.rubyforge.org/SyslogLogger/), except it doesn't need a syslog daemon running, such that your log come out exactly like syslog logs.

Mostly, this is intended to let you use tools that assume your log are in this syslog format, including:

See initial announcement here: nubyonrails.com/articles/a-hodel-3000-compliant-logger-for-the-rest-of-us

Installation and configuration

gem install hodel_3000_compliant_logger

The main thing hodel_3000_complaint_logger provides is the Hodel3000CompliantLogger class. It's a subclass of Logger (ruby-doc.org/core/classes/Logger.html), so you can use it as you would any Logger, really, except it outputs slightly different.

require 'hodel_3000_compliant_logger'
log = Hodel3000CompliantLogger.new(STDOUT)
log.level = Logger::WARN

log.debug("Created logger")
log.info("Program started")
log.warn("Nothing to do!")

To use hodel_3000_complaint_logger in Rails 4 as a replacement for the default logger, place the following line in your config/application.rb:

config.logger = Hodel3000CompliantLogger.new(config.paths['log'].first)

In Rails 3, use the following line instead (in config/application.rb):

config.logger = Hodel3000CompliantLogger.new(config.paths.log.first)

In Rails 2, instead use the following in your config/environment.rb file:

config.logger = Hodel3000CompliantLogger.new(config.paths.log.first)

NOTE

If you are using FastCGI, you may need to hard-code the hostname instead of using Socket.gethostname

Author

Geoffrey Grosenbach, with help from Eric Hodel

topfunky.com

Changes

  • Nov 29, 2007: Improvements and spec from Chris Bernard [logicleaf.com/]