Class LoggerLayoutPattern

Description

A flexible layout configurable with pattern string.

Example:

  1. require_once dirname(__FILE__).'/../../main/php/Logger.php';
  2.  
  3. Logger::configure(dirname(__FILE__).'/../resources/layout_pattern.properties');
  4. $logger Logger::getRootLogger();
  5. $logger->info("Hello World!");
  6. $logger->debug("Second line");

with the following properties file:

  1. log4php.appender.default = LoggerAppenderEcho
  2. log4php.appender.default.layout = LoggerLayoutPattern
  3. log4php.appender.default.layout.ConversionPattern = "%d{ISO8601} [%p] %c: %m (at %F line %L)%n"
  4. log4php.rootLogger = DEBUG, default

would print the following:

 2009-09-09 00:27:35,787 [INFO] root: Hello World! (at src/examples/php/layout_pattern.php line 6)
 2009-09-09 00:27:35,787 [DEBUG] root: Second line (at src/examples/php/layout_pattern.php line 7)
The conversion pattern is closely related to the conversion pattern of the printf function in C. A conversion pattern is composed of literal text and format control expressions called conversion specifiers. You are free to insert any literal text within the conversion pattern.

Each conversion specifier starts with a percent sign (%) and is followed by optional format modifiers and a conversion character.

The conversion character specifies the type of data, e.g. category, priority, date, thread name. The format modifiers control such things as field width, padding, left and right justification.

Note that there is no explicit separator between text and conversion specifiers.

The pattern parser knows when it has reached the end of a conversion specifier when it reads a conversion character. In the example above the conversion specifier %-5p means the priority of the logging event should be left justified to a width of five characters.

Not all log4j conversion characters are implemented. The recognized conversion characters are:

  • c Used to output the category of the logging event. The category conversion specifier can be optionally followed by precision specifier, that is a decimal constant in brackets. If a precision specifier is given, then only the corresponding number of right most components of the category name will be printed. By default the category name is printed in full. For example, for the category name "a.b.c" the pattern %c{2} will output "b.c".
  • C Used to output the fully qualified class name of the caller issuing the logging request. This conversion specifier can be optionally followed by precision specifier, that is a decimal constant in brackets. If a precision specifier is given, then only the corresponding number of right most components of the class name will be printed. By default the class name is output in fully qualified form. For example, for the class name "org.apache.xyz.SomeClass", the pattern %C{1} will output "SomeClass".
  • d Used to output the date of the logging event. The date conversion specifier may be followed by a date format specifier enclosed between braces. The format specifier follows the http://www.php.net/date function. Note that the special character u is used to as microseconds replacement (to avoid replacement, use \u). For example, %d{H:i:s,u} or %d{d M Y H:i:s,u}. If no date format specifier is given then ISO8601 format is assumed. The date format specifier admits the same syntax as the time pattern string of the SimpleDateFormat. It is recommended to use the predefined log4php date formatters. These can be specified using one of the strings "ABSOLUTE", "DATE" and "ISO8601" for specifying AbsoluteTimeDateFormat, DateTimeDateFormat and respectively ISO8601DateFormat. For example, %d{ISO8601} or %d{ABSOLUTE}.
  • F Used to output the file name where the logging request was issued.
  • l Used to output location information of the caller which generated the logging event.
  • L Used to output the line number from where the logging request was issued.
  • m Used to output the application supplied message associated with the logging event.
  • M Used to output the method name where the logging request was issued.
  • p Used to output the priority of the logging event.
  • r Used to output the number of milliseconds elapsed since the start of the application until the creation of the logging event.
  • t Used to output the name of the thread that generated the logging event.
  • x Used to output the NDC (nested diagnostic context) associated with the thread that generated the logging event.
  • X Used to output the MDC (mapped diagnostic context) associated with the thread that generated the logging event. The X conversion character must be followed by the key for the map placed between braces, as in %X{clientNumber} where clientNumber is the key. The value in the MDC corresponding to the key will be output. See LoggerMDC class for more details.
  • % The sequence %% outputs a single percent sign.
By default the relevant information is output as is. However, with the aid of format modifiers it is possible to change the minimum field width, the maximum field width and justification.

The optional format modifier is placed between the percent sign and the conversion character.

The first optional format modifier is the left justification flag which is just the minus (-) character. Then comes the optional minimum field width modifier. This is a decimal constant that represents the minimum number of characters to output. If the data item requires fewer characters, it is padded on either the left or the right until the minimum width is reached. The default is to pad on the left (right justify) but you can specify right padding with the left justification flag. The padding character is space. If the data item is larger than the minimum field width, the field is expanded to accommodate the data. The value is never truncated.

This behavior can be changed using the maximum field width modifier which is designated by a period followed by a decimal constant. If the data item is longer than the maximum field, then the extra characters are removed from the beginning of the data item and not from the end. For example, it the maximum field width is eight and the data item is ten characters long, then the first two characters of the data item are dropped. This behavior deviates from the printf function in C where truncation is done from the end.

Below are various format modifier examples for the category conversion specifier.

   Format modifier  left justify  minimum width  maximum width  comment
   %20c             false         20             none           Left pad with spaces if the category name
                                                                is less than 20 characters long.
   %-20c            true          20             none           Right pad with spaces if the category name
                                                                is less than 20 characters long.
   %.30c            NA            none           30             Truncate from the beginning if the category name
                                                                is longer than 30 characters.
   %20.30c          false         20             30             Left pad with spaces if the category name
                                                                is shorter than 20 characters.
                                                                However, if category name is longer than 30 chars,
                                                                then truncate from the beginning.
   %-20.30c         true          20             30             Right pad with spaces if the category name is
                                                                shorter than 20 chars.
                                                                However, if category name is longer than 30 chars,
                                                                then truncate from the beginning.

  • version: $Revision: 1213283 $
  • since: 0.3

Located in /layouts/LoggerLayoutPattern.php (line 138)

LoggerConfigurable
   |
   --LoggerLayout
      |
      --LoggerLayoutPattern
Class Constant Summary
 TTCC_CONVERSION_PATTERN = '%d [%t] %p %c %x - %m%n'
Variable Summary
Method Summary
string format (LoggerLoggingEvent $event)
array(string) formatToArray (LoggerLoggingEvent $event)
void setConversionPattern ( $conversionPattern)
Variables
LoggerPatternConverter $head (line 152)

Head of a chain of Converters.

  • access: private
mixed $pattern = self::DEFAULT_CONVERSION_PATTERN (line 146)

The conversion pattern.

  • access: protected
Methods
format (line 171)

Produces a formatted string as specified by the conversion pattern.

  • access: public
string format (LoggerLoggingEvent $event)

Redefinition of:
LoggerLayout::format()
Override this method to create your own layout format.
formatToArray (line 191)

Returns an array with the formatted elements.

This method is mainly used for the prepared statements of {@see LoggerAppenderPDO}.

It requires $this->pattern to be a comma separated string of patterns like e.g.

  1. %d,%c,%p,%m,%t,%F,%L
.

  • return: An array of the converted elements i.e. timestamp, message, filename etc.
  • access: public
array(string) formatToArray (LoggerLoggingEvent $event)
setConversionPattern (line 159)

Set the ConversionPattern option. This is the string which controls formatting and consists of a mix of literal content and conversion specifiers.

  • access: public
void setConversionPattern ( $conversionPattern)
  • $conversionPattern

Inherited Methods

Inherited From LoggerLayout

LoggerLayout::activateOptions()
LoggerLayout::format()
LoggerLayout::getContentType()
LoggerLayout::getFooter()
LoggerLayout::getHeader()
LoggerLayout::warn()

Inherited From LoggerConfigurable

LoggerConfigurable::setBoolean()
LoggerConfigurable::setFileSize()
LoggerConfigurable::setInteger()
LoggerConfigurable::setLevel()
LoggerConfigurable::setNumeric()
LoggerConfigurable::setPositiveInteger()
LoggerConfigurable::setString()
LoggerConfigurable::warn()
Class Constants
DEFAULT_CONVERSION_PATTERN = '%m%n' (line 140)

Default conversion Pattern

TTCC_CONVERSION_PATTERN = '%d [%t] %p %c %x - %m%n' (line 143)

Default conversion TTCC Pattern

Documentation generated on Sat, 18 Feb 2012 22:32:24 +0000 by phpDocumentor 1.4.3