#111332Provide central read access to sys_log
Description
Problem
Writes to sys_log are partly encapsulated (TYPO3\CMS\Core\SysLog\Repository\LogEntryRepository, see change 92211), but reads are not. Several places outside EXT:belog build their own queries against the table:
EXT:dashboard:NumberOfFailedLoginsDataProvider,SysLogErrorsDataProvider,LatestBeLoginsDataProviderEXT:backend:FailedLoginAttemptNotificationEXT:core:DataHandler::printLogErrorMessages()EXT:lowlevel:ListSysLogCommandEXT:belog:SystemInformationEventListener
Every consumer depends on the table layout and the meaning of type, action, error, channel and level. This makes the table hard to evolve alongside the Logging API work in v15, and it leads to the same data being presented inconsistently (see the discussion on the “Activity Stream” widget, #107918).
Proposal
Provide one core read-side access point for sys_log, next to the existing write-side repository, and migrate consumers to it step by step. The API is internal at first and must not change the behaviour of any consumer.
Reviews 1
History 23
-
Sebastian Michaelsen changed category <span data-processor="relativetime" data-value="2026-11-03T14:05:10+00:00" > 11/03/26, 14:05 </span>
-
Sebastian Michaelsen changed description <span data-processor="relativetime" data-value="2026-11-03T14:10:51+00:00" > 11/03/26, 14:10 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 97324 status
NewUnder Review <span data-processor="relativetime" data-value="2026-11-03T14:43:55+00:00" > 11/03/26, 14:43 </span>