Log/Log4perl/FAQ.pm

14 be just a matter of smartly configuring your Log::Log4perl configuration files.
70 pulls in C<use Log::Log4perl qw(:easy)> first, then you're set.
97 behavior by passing in a configuration to its C<init> method as a string
103         # Define configuration
127 takes the name of a configuration file as its input parameter like
132 the example above shows how to pass in a configuration as text in a
135 The configuration as shown
151 Appender settings in the configuration are defined as follows:
159 have to explicitly set the appropriate C<Log::Log4perl::Appender::File>
166 Also, the configuration defines a PatternLayout format, adding
272 do you? Instead, you want to set it in a global data structure and
274 in the configuration file:
280 you've set once via
301 Assuming that you already have a Log4perl configuration file like
313 just add another appender to the configuration file and you're done:
327 The configuration file above is assuming that both appenders are
353 Log::Log4perl configuration and then call Perl's C<die()>
407 which defaults to 0, but can be set to positive integer values
578 =head2 What if I need dynamic values in a static Log4perl configuration file?
581 therefore comes with a Log4perl configuration file, specifying the logging
583 But, you also want it to take command line parameters to set values
586 both a static Log4perl configuration file and a dynamic command line
589 As of Log::Log4perl 0.28, every value in the configuration file
606 When C<Log::Log4perl-E<gt>init()> parses the configuration
686 all you have to do is specify it in your Log::Log4perl configuration file
693 the oldest ones. If you set the C<max> parameter to 2 and the name of
702 Here's an example of a Log::Log4perl configuration file, defining a
719 =head2 What's the easiest way to turn off all logging, even with a lengthy Log4perl configuration file?
730 anywhere in your configuration file will limit any output to any appender
742 somewhere in your Log::Log4perl configuration, the system will be quiet
745 logging messages according to the rest of the configuration file again.
750 configuration file sometimes leads to a phenomenon called
756 Here's a sample Log4perl configuration file that produces the
768 is set to the lower C<WARN> level.
796 hierarchy is to set the C<additivity> flag of the subordinate logger to
814 higher-level appender. Typically it is set to be
857 configuration file:
883 First off, Log::Log4perl comes with a set of standard appenders. Then,
906 configuration file C<test.conf> looks like this:
930 and pass all attributes of the appender as defined in the configuration
961 The color (as configured in the Log::Log4perl configuration file)
1076 to the configuration above, and you'll get what you wanted in the
1125 a configuration parameter C<maxcount> which defaults to 5 in the
1126 snippet above but can be set in the Log4perl configuration file like this:
1169 defined by the C<maxcount> configuration parameter.
1206 their exposure via the appender threshold mechanism and set
1252 =head2 On our server farm, Log::Log4perl configuration files differ slightly from host to host. Can I roll them all into one?
1257 configuration files for every host and specify the value like
1263 figure out the IP address at configuration time and set the appender's
1276 once at configuration time (not runtime!) and its return value is
1278 for rolling out applications whichs Log::Log4perl configuration files
1284 If you're using Log4perl's feature to specify the configuration as a
1285 string in your program (as opposed to a separate configuration file),
1372 The last four statements in the configuration above are defining a custom
1479 appender so you don't have to set it explicitely.)
1496 Here's a sample configuration to synchronize access to a file appender:
1545 (see http://jakarta.apache.org/log4j ). Create a configuration file like
1547   <log4j:configuration debug="true">
1554   </log4j:configuration>
1558   java -Dlog4j.debug=true -Dlog4j.configuration=config.xml \
1636 approach: although every process has a separate L4p configuration,
1684 gets set back after the handler exits.
1692 you'll get (depending on your Log::Log4perl configuration) something like
1789 appender classes found in its configuration. If you specify
1828 =head2 How can I access a custom appender defined in the configuration?
1830 Any appender defined in the configuration file or somewhere in the code
1932 its permissions are set to C<rw-r--r-->. Why? Because your
1995 set to utf-8 mode:
1997       # Either in the log4perl configuration file:
2007 If the complaining appender is a screen appender, set its C<utf8> option:
2026 all is well, because STDOUT is by default set to byte mode. However,
2085 threshold set to ERROR, the second appender will filter the messages
2112 Then set your /etc/log4perl.conf file to include:
2134 file appender's C<recreate> option needs to be set to a true value:
2144 change this interval, the option C<recreate_check_interval> can be set
2146 check should be performed before every write, it can even be set to 0:
2152 handler can be set up:
2172 For example, with a newsyslog configuration like
2205 applies for the short time frame of C<recreate_check_interval> seconds
2208 To make sure that no messages get lost, one option is to set the
2224     # newsyslog.conf configuration for compressing archive files and
2254 has an C<umask> option that can be set to support this:
2315 If you want UTC instead, set
2570 to end up at? STDOUT? STDERR? And are you sure you want to set in stone
2581 fires if the system log level is set to $OFF: