(forwarding to davis mcpherson this time)
> i dont think setting to 'debug' will work properly as the apache logging
> code really needs to know the correct level of the log message and this
> is indicated by the method called...
I didn't see the original post so forgive me if I'm missing the point,
but if the only thing ApacheLog needs to know the log level for is to
decide whether or not to log the statement (and from reading the docs I
think that's right) then you should be able to turn the Apache logging
level all the way up, open that valve completely as it were, because the
decision whether or not to log is now being made by log4perl. We've put
another valve on the pipe before the ApacheLog valve.
Basically you're not controlling the logging from the apache config
anymore, you're controlling it from the log4perl config.
However, if ApacheLog is doing something else with the level, like
making it part of the error message or doing different routing for
different levels, then that's a horse of a different color. For
instance, the current problem with using Log::Dispatch::DBI is that it
does something like
INSERT INTO logtable (level, msg) values (?,?)
but the level that Log::Dispatch::DBI gets from Log4perl is always
'debug', so it's less than helpful.
> i'm certainly not at expert in this area but it seems logging with the
> Log::Dispatch::ApacheLog is a unique case (certainly more complex than
> SCREEN, FILE, EMAIL, etc....do
Pardon my dumb question, but how is ApacheLog different? To log or not
to log, that is the question, but it's decided by Log4perl before
ApacheLog ever even hears about it.
--
Happy Trails . . .
Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA 94706
(510) 525-5217
--
Happy Trails . . .
Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA 94706
(510) 525-5217
|
