You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
We are using ShortenedThrowableConverter and it can exclude lines in the stack trace, but we need to suppress the actual exception messages.
The Ask:
Because we work in cloud service and have to be VERY careful what appears in the logs, we sometime cannot log the full stacktrace with detailed message. We would like a way to indicate that certain log messages need to print the stack trace with java classnames and line numbers, but not print ANY detailed messages in the entire stack trace. This includes Caused By exceptions, etc. This suppression might be triggered with the use of a logback Marker. One could ask- if you get rid of the message, is it even still helpful? Yes, it is better than nothing. We would still be able to the java class/Exception type that was thrown and the location in the code it came from.
We have looked into extending and overriding ShortenedThrowableConverter to accomplish this, but the methods we need to get to are private. If there is another existing way to accomplish this, please let me know!
The text was updated successfully, but these errors were encountered:
Problem:
We are using ShortenedThrowableConverter and it can exclude lines in the stack trace, but we need to suppress the actual exception messages.
The Ask:
Because we work in cloud service and have to be VERY careful what appears in the logs, we sometime cannot log the full stacktrace with detailed message. We would like a way to indicate that certain log messages need to print the stack trace with java classnames and line numbers, but not print ANY detailed messages in the entire stack trace. This includes Caused By exceptions, etc. This suppression might be triggered with the use of a logback Marker. One could ask- if you get rid of the message, is it even still helpful? Yes, it is better than nothing. We would still be able to the java class/Exception type that was thrown and the location in the code it came from.
We have looked into extending and overriding ShortenedThrowableConverter to accomplish this, but the methods we need to get to are private. If there is another existing way to accomplish this, please let me know!
The text was updated successfully, but these errors were encountered: