Re: [log4perl-devel] Using one config for multiple hosts and multiple applications

[Karsten H. <kar...@bl...>]

Hi Mike,

thanks for the reply!

Mike Schilli <m...@pe...> writes:
> On Mon, 19 Jan 2009, Karsten Heymann wrote:
>> The scripts run on multiple hosts and belong to several sets of
>> projects with different logging requirements. To simplify the
>> setup, I'm trying to use only one L4p config file for the whole
>> setup. First of all, is this common practise?

> It's certainly possible to do that, you just need to weigh easy
> deployment against maintainability of the config file. This might
> work for two scripts, but if you have 100, it might become unwieldy.

Okay, this forces me to rethink our logging architecture.

> [...]  one way of doing what you want would be using a file name
> that depends on the calling script [...]

We did that before but ran into problems with file rights (cgi-scripts
running with www-data, developers testing the scripts as themselves)
so we decided to go to use syslog as main logging target. This also
allows us to use a centralized loghost, which together with a web
syslog front end, should make searching the logs much easier in the
long run. Although this would mean that a separate log file would be
created for *all* scripts called with this setup.

There also is another reason for a central l4p setup: All errors in
production scripts are supposed to be logged in the same way (to allow
some kind of automatic alarming). I don't want to repeat that part of
the config for any l4p config file.

>> What also is missing is the ability to source additional l4p
>> files. This would allow to ship a unchanged master file on all
>> servers and include a file with local changes at the end. From what
>> I read this isn't possible, unless i did oversee something?
>
> Nobody stops you from reading in all *.conf files located in a conf
> directory, lumping them together to a long string and feeding it to
> Log4perl via ->init(\$string), but this will most likely be better
> supported in the future.

Good idea, I didn't think of that.

Yours
Karsten
-- 
Karsten Heymann