Issue Task Under Review Quiet

#111332Provide central read access to sys_log

Sebastian Michaelsen 11/03/26, 14:04 updated 11/03/26, 14:43

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, LatestBeLoginsDataProvider
  • EXT:backend: FailedLoginAttemptNotification
  • EXT:core: DataHandler::printLogErrorMessages()
  • EXT:lowlevel: ListSysLogCommand
  • EXT: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