[gorpovitch]

When using a tool like Sentry, you might want to logger.exception(e) instead of a string error message, that way the whole stack trace with helpful debugging information (local variables...) is included in Sentry.

[tmarice]

logger.exception is basically a shortcut for logger.error(exc_info=True), so there's no need for explicitly assigning e as an error message.

[aidos]

And if you look carefully you’ll find that doing logger.exception(e) will just cast e as a string, which is just the message in the e. So you end up just sending the message twice (along with the stack trace).

Instead you can do logger.exception(“something helpful to give a little more context at a glance”)

[nicbou]

You might also want to use formatted strings too as it allows some logging tools to group the messages together.