We want to use Sentry to log (useful) throwables. For containerized deployments there should be no local files written with exception information. We should investigate the idea if we could refactor the implementation to override the logger throwable storage class and use Sentry (with an ignore list of not very useful exceptions like "asset not found").
This should only happen if a Sentry DSN is set - otherwise the exception should be logged (console or log file).
Maybe we could get rid of the Debug / Production Exception Handlers.
Idea:
We want to use Sentry to log (useful) throwables. For containerized deployments there should be no local files written with exception information. We should investigate the idea if we could refactor the implementation to override the logger throwable storage class and use Sentry (with an ignore list of not very useful exceptions like "asset not found").
This should only happen if a Sentry DSN is set - otherwise the exception should be logged (console or log file).
Maybe we could get rid of the Debug / Production Exception Handlers.