Frontend plugin exceptions not generating backend notifications in TYPO3

The goal is to ensure that administrators are alerted in the TYPO3 backend Notification Center when an unhandled exception occurs in a frontend plugin, without contributing to notification noise.

Currently, frontend exceptions are written to the sys_log table via the core logging framework, but they do not automatically trigger a backend notification. Administrators must manually check the Log module or the Status Report to become aware of these issues. This behavior creates a gap between error detection and operational awareness, especially when log levels are tuned to file‑based writers for DEBUG/INFO while only WARNING+ entries populate sys_log.

Constraints include preserving the existing log writer configuration (e.g., rotating file logs for low‑severity messages), avoiding excessive flash messages that could obscure critical alerts, and respecting TSconfig options such as hideNotification that may suppress notifications for specific modules or user groups. It is also unclear whether extending the logging framework with a notification listener, configuring the Notification Center to poll sys_log entries above a certain severity, or creating a dedicated Scheduler task would be the most appropriate solution.

Which configuration options exist to route frontend exceptions to the backend notification system? How can log level thresholds be set so that only exceptions of WARNING or higher generate a backend notification? What TSconfig or extension settings can suppress low‑priority noise while still ensuring critical frontend errors are surfaced?