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
if he/she wants to log unexpected exceptions from annotated handler methods.
By default (e.g. in spring-graphql sample apps) exceptions are not written to log .
Is it how it's intended to be? I would expect unexpected application errors to be written to log by default.
The text was updated successfully, but these errors were encountered:
Thanks for the question, this can be improved as follows.
If the exception is resolved by a DataFetcherExceptionResolver it is logged with a stack trace at DEBUG level. If the exception is unresolved, in which case default handling as as internal error applies, then it is logged with a stack trace at ERROR level.
I think this is what you expect as well but if not please comment.
rstoyanchev
changed the title
Exception logging - default behavior
Improve Exception Logging in ExceptionResolversExceptionHandler
Apr 13, 2022
As I understand, currently developer has to set this application settting:
if he/she wants to log unexpected exceptions from annotated handler methods.
By default (e.g. in spring-graphql sample apps) exceptions are not written to log .
Is it how it's intended to be? I would expect unexpected application errors to be written to log by default.
The text was updated successfully, but these errors were encountered: