洞察探索open banking如何通过小程序容器技术助力金融企业实现数据安全和数字化转型
820
2022-10-26
Log4r - 使用Ruby程序一个全面的和灵活的日志库
Log4r - A flexible logging library for Ruby
This release | 1.1.11 |
Release date | 04/Jan/2014 |
License | BSD |
Maintainer | Colby Gutierrez-Kraybill |
Contributor | |
---|---|
Leon Torres | Original Maintainer |
Martain Stannard | RollingFileOutputter |
Steve Lumos | SyslogOutputter |
Mark Lewandowski | ScribeOutputter |
Andreas Hund | YamlConfigurator |
Jamis Buck | log4r.gemspec |
Charles Strahan | log4jxml/chainsaw integration |
Nitay Joffe | STARTTLS |
David Siegal | Smart updates to RollingFileOutputter |
Summary
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.
Requirements
(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
More Info
Installation instructions are in the file INSTALLComprehensive examples are provided in examples/ and can be run right awayLog4r homepage: doc/index.htmlManual: doc/manual.htmlRDoc API reference: doc/rdoc/index.htmlThe changelogFeel free to bug the maintainer with any questions (listed at top of file)
Usability
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.
Platform Issues
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. :)
版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。
发表评论
暂时没有评论,来抢沙发吧~