Re: subclassing Logging

On May 1, 11:29=A0am, Tim Pease <[e-mail]> wrote:
> On Apr 30, 2010, at 11:23 PM, [e-mail] wrote:
>
>
>
> > Tim,
>
> > I am trying to subclass the logging module to have a consistent setup f=
or my classes. They all log to the same rolling file. =A0I seem to get two =
different errors.
>
> > Error one:
> > require 'fileutils'
> > require 'logging'
>
> > module MyLogger
> > class Log < Logging::Logger
> > =A0def initialize(config) =A0# config not used in test but will be.
> > =A0 =A0super("reader")
> > =A0 =A0Logging.appenders.stdout(:level =3D> :debug)
> > =A0 =A0file_path =3D =A0"./reader.log"
> > =A0 =A0Logging.appenders.rolling_file(
> > =A0 =A0"readerlog",
> > =A0 =A0:filename =3D> file_path,
> > =A0 =A0:age =3D> :daily,
> > =A0 =A0:layout =3D> Logging.layouts.json)
> > =A0 =A0add_appenders('stdout','readerlog')
> > =A0end
> > end
> > end
>
> Take a look at this example logging configuration. It walks though the co=
ncept of logger hierarchies in the logging framework.
>
> http://github.com/TwP/logging/blob/master/examples/hierarchies.rb
>
> This, I believe, is what you are trying to accomplish. You should not hav=
e to subclass the Logging:Logger. Take a look at the other example files in=
 that "examples" folder; they walk through in code some of the concepts beh=
ind the logging framework.
>
> Logging.appenders.stdout(
> =A0 'stdout',
> =A0 :layout =3D> Logging.layouts.pattern
> )
>
> Logging.appenders.rolling_file(
> =A0 'readerlog',
> =A0 :filename =3D> './reader.log',
> =A0 :age =3D> :daily,
> =A0 :layout =3D> Logging.layouts.json
> )
>
> logger =3D Logging.logger['YourModule']
> logger.appenders =3D ['stdout', 'readerlog']
> logger.level =3D :info
>
> In the above snippet of code, I created two appenders. The first is named=
 "stdout" and will use a pattern based layout to write log messages to STDO=
UT. The second is named "readerlog" and will use a JSON layout to write log=
 messages to a file called "reader.log".
>
> I then created a new logger instance, added the two appenders by name, an=
d then set the log level to 'info'.
>
> Now you can create nested loggers that will use the same appenders and ha=
ve the same default log level.
>
> another_logger =3D Logging.logger['YourModule::Another']
> yet_another_logger =3D Logging.logger['YourModule::Another::Yet']
>
> > with this in a larger program or by it self I get:
>
> > NoMethodError: undefined method `synchronize' for nil:NilClass
> > =A0 =A0 =A0 =A0from /usr/local/ruby/lib/ruby/gems/1.8/gems/logging-1.4.=
1/lib/logging/logger.rb:51:in `new'
> > =A0 =A0 =A0 =A0from (irb):2
> > irb command is =A0l =3D =A0MyLogger::Log.new('test')
>
> > If I remove the parameter from the initialize, I can make it work stand=
alone.
>
> > I tried using rspec in the larger app and just the test for log fails t=
he same with the parameter. =A0I take it off and the init passes but the ac=
tual log does not return.
>
> The Logging framework has built in support for rspec. It can be configure=
d to log all messages to a StringIO instance during tests. You can then rea=
d out your log messages from the StringIO and make sure the right messages =
are making it into the log.
>
> In your spec_helper file ....
>
> require 'spec/logging_helper'
>
> Spec::Runner.configure do |config|
> =A0 include Spec::LoggingHelper
> =A0 config.capture_log_messages
> end
>
> And in your actual specs ...
>
> it 'logs a message on error' do
> =A0 @foo.error_method
> =A0 @log_output.readline.should =3D=3D 'This is your error message'
> end
>
> I hope all this helps.
>
> Blessings,
> TwP
>
> PS =A0I cc'd the ruby-talk mailing list so this information can be found =
by others.
>
> > describe MyLogger::Log do
> > =A0it "should initialize" do
> > =A0 =A0l =3D MyLogger::Log.new()
> > =A0 =A0l.class.should =3D=3D MyLogger::Log
> > =A0end
> > end
>
> > describe MyLogger::Log do
> > =A0before :each do
> > =A0 =A0@log =3D MyLogger::Log.new
> > =A0end
>
> > =A0it "should log a debug" do
> > =A0 =[e-mail] "Rspec debug".should =3D=3D true
> > =A0end
>
> > end
>
> > the @log.info fails with:
> > 'MyLogger::Log should log a debug' FAILED
> > expected: true,
> > =A0 =A0 got: "Rspec debug" (using =3D=3D)
>
> > I can use any help you can give.
>
> > Don French
>
>

Thanks for the information.

This is the structure. The live processor (could be several) are
instantiated my main and need to log what happens in their own
processor. Same thing with the test processor. Can the two "reader"
logger ids be configured different? In testing it seems that all write
to all the log files.  If I change the top level name, how does the
lower level objects know what the top level is?  I know I can pass to
every object the mode, but really do not like doing that. They do not
care other than for logging.

main
-- live_processor           Logger['reader']  Logs into a file called
live_tag.log tag changes for each live processor instantiated.
   -- processor class      Logger['reader::processor']
	-- class_1                Logger['reader::processor::class_1']   or
can I just do 'reader::processor'
	    |	-- class_2
	    |		|
           |            |
	    |	-- class_x
	-- class_y
-- test_processor		Logger['reader']   Logs into a file called test.log
	-- class_1		Logger['reader::processor']
	    |	-- class_2	Logger['reader::processor::class_1']   or can I just
do 'reader::processor'
	    |		|
           |            |
	    |	-- class_x
	-- class_y


Thanks

Don