Bug #89120

Loggers miss the requestId

Added by Helmut Hummel almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-09-09
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Because requestId is now an (optional) constructor argument of LogManager, but LogManager is instantiated by the bootstrap
first without this argument, the requestId remains empty.

The LogManager is indirectly instantiated the first time when error handling is set up and a logger is injected into ErrorHandler


Related issues

Related to TYPO3 Core - Task #84082: A LogRecord should not rely on global state (requestId from Bootstrap)Closed2018-02-28

Actions

Also available in: Atom PDF