Logging version 1.0.0 by Tim P. http://logging.rubyforge.org/ == DESCRIPTION Logging is a flexible logging library for use in Ruby programs based on the design of Java's log4j library. It features a hierarchical logging system, custom level names, multiple output destinations per log event, custom formatting, and more. == CHANGES 2 major enhancements - Refactored access to the appenders - Created a much cleaner way to initialize the logging framework 3 minor enhancements - Added a YAML layout option - Added a JSON layout option - Cration of an "examples" directory 1 bug fix - Logging initialization happens implicitly when a logger, layout, or appender is created == NOTES There are two new layouts for outputting logs as using parseable formats -- JSON and YAML. This is very nice when you want to sift through very large log files looking for specific messages or sequences of messages. No more messy regular expressions. Just use a JSON parser or a YAML parser to ingest the log messages. There are quite a few examples of how to use the logging framework in the "examples" directory. Please take a look at the source package to get some ideas and inspiration. The examples also show the favored way for configuring the logging framework. Please take a look. This release will introdcue backwards incompatabilities with regard to accessing the STDOUT and STDERR appenders. The two lines below show the old way and the new way: Logging::Appender.stdout # old way that no longer works Logging.appenders.stdout # new way (similar for stderr) == THANKS Ara T. Howard gave a great talk about boulder.rb the other night. Inspiration from that meeting was the germ of this update. Blessings, TwP
on 2009-04-18 09:07
on 2009-04-18 19:53
On Fri, Apr 17, 2009 at 10:07 PM, Tim P. <email@example.com> wrote: > Logging version 1.0.0 > by Tim P. > http://logging.rubyforge.org/ > > == DESCRIPTION > > Logging is a flexible logging library for use in Ruby programs based on the > design of Java's log4j library. It features a hierarchical logging system, > custom level names, multiple output destinations per log event, custom > formatting, and more. Hey Tim, How does logging compare to log4r?
on 2009-04-18 21:43
On Sat, Apr 18, 2009 at 9:52 AM, Aaron T. <firstname.lastname@example.org> wrote: >> formatting, and more. > > Hey Tim, > How does logging compare to log4r? > Let's find out 'logging' <=> 'log4r' #=> 1 Logging supports all the same features of log4r and some improvements and nifty new things, too. The rolling log file appender in Logging is safe to use from multiple processes; this is not the case with log4r's rolling file outputter. Logging supports parseable log formats -- messages can be output as JSON or YAML formatted objects. This makes parsing your log files much much easier. Logging has a growl notification appender for those of you on Mac OS X. Both support logger hierarchies. Logging has a cleaner interface (in my opinion). Check out the examples folder of the logging project to get a feel of how to use it and what it is capable of. http://github.com/TwP/logging/tree/master Blessings, TwP