- Issue created by @smustgrave
- Status changed to Closed: duplicate
10 months ago 3:49pm 16 November 2023
Follow up from β¨ Display backtrace for logged throwables on log message details page Fixed
@xjm @alexpott Looking at core/lib/Drupal/Core/EventSubscriber/ExceptionLoggingSubscriber.php I do see one place where we could consider removing @backtrace_string from the context array: The ExceptionLoggingSubscriber::onClientError() method.
It's already removed in the ExceptionLoggingSubscriber::on403() method.
This would clean up the UI by removing the backtrace for miscellaneous 4xx errors (e.g. \Symfony\Component\HttpKernel\Exception\UnsupportedMediaTypeHttpException) logged by this mechanism, and would reduce storage size of dblog module going forward, for sites that have been getting lots of non-404/403 4xx errors.
TBD
Determine if we should remove - IMPORTANT
Review
Review
NA
NA
NA
NA
Closed: duplicate
11.0 π₯