A way to expose logger.exception message first in Sentry

[warvariuc]

I am logging an exception for a function like this:

try:
    handler_obj.execute()
except Exception:  # pylint: disable=broad-except
    logger.exception("EventBridge handler %s error", handler_obj.__class__.__name__)

I provided a message to see the context of the exception in emails, Slack, etc., to know immediately where the particular exception happened.

Unfortunately, Sentry exposes the exception message first, hiding my message inside:

So I see ConnectionError in Slack, but this tells me nothing about the context.

Is there a way to expose the provided EventBridge handler %s error in Sentry ?