[Feature]: Option to remove stack trace from exception logging

[scraymondjr]

The Feature

There does not appear to be any option to remove stack traces from exceptions when they are logged. This causes the function arguments to be logged, which defeats the purpose of the message redaction option (turn_off_message_logging) since the message content is still logged via the exception stack trace.

I propose that the turn_off_message_logging option include disable stack trace logging with another option to force the stack trace to be enabled if so desired (always_include_stack_trace or something). This would help to ensure that incoming messages are never logged, while allowing an option for the stack trace to remain if so desired.

I have attached a screenshot of a message sent to Sentry that shows the stack trace with the complete incoming request arguments available, even though turn_off_message_logging is set to true.

Motivation, pitch

If using the turn_off_message_logging option, then it may be presumed that there is a desire to avoid logging any user provided values. There should be a means for ensuring that absolutely no user provided values are logged for privacy conscious applications.

Are you a ML Ops Team?

Yes

Twitter / LinkedIn details

No response

Sample Sentry exception with stack trace