Log4r alternatives and similar gems
Based on the "Logging" category.
Alternatively, view Log4r alternatives based on common mentions on social networks and blogs.
5.6 2.1 L5 Log4r VS Semantic LoggerSemantic Logger is a feature rich logging framework, and replacement for existing Ruby & Rails loggers.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Log4r or a related project?
Log4r - A flexible logging library for Ruby
|Leon Torres||Original Maintainer|
|Charles Strahan||log4jxml/chainsaw integration|
|David Siegal||Smart updates to RollingFileOutputter|
Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations per log event, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more.
- (required) Ruby >= 1.7.0 (use log4r 1.0.2 for Ruby 1.6)
- (optional) RubyGems for installing Log4r as a gem
- (optional) Ruby syslog library for SyslogOutputter
- (optional) XML configuration requires REXML
- (optional) log4j chainsaw integration requires 'builder' >= 2.0
- (optional) STARTTLS email login, requires 'smtp_tls" if Ruby <= 1.8.6
- Installation instructions are in the file INSTALL
- Comprehensive examples are provided in examples/ and can be run right away
- Log4r homepage: doc/index.html
- Manual: doc/manual.html
- RDoc API reference: doc/rdoc/index.html
- The changelog
- Feel free to bug the maintainer with any questions (listed at top of file)
Log4r works really well, so please take advantage of it right away! :) All versions since 0.9.2 have been stable and backward-compatible. The code is stable enough that updates are infrequent and usually only for adding features or keeping the code up to date with Ruby.
Log4r is known to work on Linux and WindowsXP. It's safe to assume that Log4r will work on any Ruby-supported platform.
When Trouble Strikes
Log4r comes with an internal logger. To see its output, create a logger named 'log4r' before any others and give it a suitable outputter,
trouble = Logger.new['log4r'] trouble.add Outputter.stdout
Try running the unit tests provided (run the file tests/runtest.rb). Let the maintainer know what's up and feel free to explore and fix the code yourself. It's well documented and written in Ruby. :)
*Note that all licence references and agreements mentioned in the Log4r README section above are relevant to that project's source code only.