|
NAMELog::Report::Dispatcher::Log4perl - send messages to Log::Log4perl back-endINHERITANCELog::Report::Dispatcher::Log4perl is a Log::Report::Dispatcher SYNOPSIS# start using log4perl via a config file # The name of the dispatcher is the name of the default category. dispatcher LOG4PERL => 'logger' , accept => 'NOTICE-' , config => "$ENV{HOME}/.log.conf"; # disable default dispatcher dispatcher close => 'logger'; # configuration inline, not in file: adapted from the Log4perl manpage my $name = 'logger'; my $outfile = '/tmp/a.log'; my $config = <<__CONFIG; log4perl.category.$name = INFO, Logfile log4perl.logger.Logfile = Log::Log4perl::Appender::File log4perl.logger.Logfile.filename = $outfn log4perl.logger.Logfile.layout = Log::Log4perl::Layout::PatternLayout log4perl.logger.Logfile.layout.ConversionPattern = %d %F{1} %L> %m __CONFIG dispatcher LOG4PERL => $name, config => \$config; DESCRIPTIONThis dispatchers produces output tot syslog, based on the "Sys::Log4perl" module (which will not be automatically installed for you).Extends "DESCRIPTION" in Log::Report::Dispatcher. Reasons <--> LevelsThe REASONs for a message in Log::Report are names quite similar to the log levels used by Log::Log4perl. The default mapping is list below. You can change the mapping using new(to_level).TRACE => $DEBUG ERROR => $ERROR ASSERT => $DEBUG FAULT => $ERROR INFO => $INFO ALERT => $FATAL NOTICE => $INFO FAILURE => $FATAL WARNING => $WARN PANIC => $FATAL MISTAKE => $WARN Categories"Log::Report" uses text-domains for translation tables. These are also used as categories for the Log4perl infrastructure. So, typically every module start with:use Log::Report 'my-text-domain', %more_options; Now, if there is a logger inside the log4perl configuration which is named 'my-text-domain', that will be used. Otherwise, the name of the dispatcher is used to select the logger. Limitiations The global $caller_depth concept of Log::Log4perl is broken. That variable is used to find the filename and line number of the logged messages. But these messages may have been caught, rerouted, eval'ed, and otherwise followed a unpredictable multi-leveled path before it reached the Log::Log4perl dispatcher. This means that layout patterns %F and %L are not useful in the generic case, maybe in your specific case. METHODSExtends "METHODS" in Log::Report::Dispatcher.ConstructorsExtends "Constructors" in Log::Report::Dispatcher.
AccessorsExtends "Accessors" in Log::Report::Dispatcher.
LoggingExtends "Logging" in Log::Report::Dispatcher.
DETAILSExtends "DETAILS" in Log::Report::Dispatcher.SEE ALSOThis module is part of Log-Report distribution version 1.33, built on July 17, 2021. Website: http://perl.overmeer.net/CPAN/LICENSECopyrights 2007-2021 by [Mark Overmeer <markov@cpan.org>]. For other contributors see ChangeLog.This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://dev.perl.org/licenses/
Visit the GSP FreeBSD Man Page Interface. |