Turn Kernel::System::Log into a wrapper around Log::Log4perl

[bschmalhofer]

Log::Log4perlgives a great amount of flexibility but is a major undertaking. This deserves its own issue.

Originally posted by @bschmalhofer in #73 (comment)

[svenoe]

I see that there could be upsides. Maybe if we use Kernel::System::Log as wrapper around Log::Log4perl? I put it to medium priority, let us discuss this at some meeting in the future.

[stefanhaerter]

Perhaps this could be useful if we implement this ome day - leaving it here: https://metacpan.org/pod/Log::Log4perl::Config::YamlConfigurator

[bschmalhofer]

I see that there could be upsides. Maybe if we use Kernel::System::Log as wrapper around Log::Log4perl? I put it to medium priority, let us discuss this at some meeting in the future.

Keeping the interface of Kernel::System::Log would be essential as otherwise all looging calls would have to updated. But that should be a thin wrapper, not like my first idea that used Log4perl as just another backend for Kernel::System::Log.

[bschmalhofer]

Perhaps this could be useful if we implement this ome day - leaving it here: https://metacpan.org/pod/Log::Log4perl::Config::YamlConfigurator

Yes, these kind of things can easily be employed with Log4perl. Another option is the Log4perl simply gets a Perl data structure as configuration.