Configuration of the logging system¶
Instantiation of Loggers is configuration-free, as the LogManager automatically applies its configuration.
The Logger configuration is read from
$GLOBALS['TYPO3_CONF_VARS']['LOG'], which contains an array reflecting the namespace
and class hierarchy of your TYPO3 project.
To apply a configuration for all Loggers within the
the configuration is read from
So every logger requested for classes like
\TYPO3\CMS\Core\Cache\Backend\NullBackend, etc. will get this configuration applied.
The same holds for the old pseudo-namespaces with underscore separator which
are still common in extensions.
Configuring Logging for extensions works the same. If an extension uses namespaces, the syntax for the configuration is as above.
For older extensions, configuration is
searched for in
$GLOBALS['TYPO3_CONF_VARS']['LOG']['Tx'] to differentiate extension classes
from Core classes (as extension class names start with
The Log Writer configuration is read from the subkey
writerConfiguration of the configuration array:
$GLOBALS['TYPO3_CONF_VARS']['LOG']['writerConfiguration'] = [ // configuration for ERROR level log entries \TYPO3\CMS\Core\Log\LogLevel::ERROR => [ // add a FileWriter \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [ // configuration for the writer 'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_7ac500bce5.log' ] ] ];
The above configuration applies to all log entries of level “ERROR” or above.
Since TYPO3 v9 the default folder for log files is
<var-path> in a non-Composer installation (Classic Mode) is
in a Composer based installation it is
<project-root>/var/ instead, unless configured otherwise.
\TYPO3\CMS\Core\Core\Environment for defaults in both cases.
Since TYPO3 v9 it is possible (and a good practice) to store temporary files
outside the document root.
To apply a special configuration for the controllers of the examples extension, use the following configuration:
$GLOBALS['TYPO3_CONF_VARS']['LOG']['Documentation']['Examples']['Controller']['writerConfiguration'] = [ // configuration for WARNING severity, including all // levels with higher severity (ERROR, CRITICAL, EMERGENCY) \TYPO3\CMS\Core\Log\LogLevel::WARNING => [ // add a SyslogWriter \TYPO3\CMS\Core\Log\Writer\SyslogWriter::class => , ], ];
This overwrites the default configuration shown in the first example for classes
located in the namespace
For extension “foo” with key “tx_foo” (not using namespaces), the configuration would be located at:
$GLOBALS['TYPO3_CONF_VARS']['LOG']['Tx']['Foo']['writerConfiguration'] = [ // ... ];
An arbitrary number of writers can be added for every severity level (INFO, WARNING, ERROR, …).
The configuration is applied to log entries of the particular severity level
plus all levels with a higher severity. Thus, a log messages created with
will be affected by the writerConfiguration for the log levels:
For the above example code that means:
$logger->warning($msg);will result in $msg being written to the computer’s syslog on top of the default configuration.
$logger->debug($msg);will result in $msg being written only to the default log file (
For a list of writers shipped with the TYPO3 Core see the section about Log Writers.
Similar to the writer configuration, log record processors can be configured on a per-class and per-namespace
basis from the subkey
$GLOBALS['TYPO3_CONF_VARS']['LOG']['Documentation']['Examples']['Controller']['processorConfiguration'] = [ // configuration for ERROR level log entries \TYPO3\CMS\Core\Log\LogLevel::ERROR => [ // add a MemoryUsageProcessor \TYPO3\CMS\Core\Log\Processor\MemoryUsageProcessor::class => [ 'formatSize' => TRUE ] ] ];
For a list of processors shipped with the TYPO3 Core, see the section about Log processors.