Skip to content

Exception not logged at DEBUG level when handled by annotated controller method #996

Closed
@lukasGemela

Description

@lukasGemela

Documentation states that:

Unresolved exception are logged at ERROR level along with the executionId to correlate to the error sent to the client. Resolved exceptions are logged at DEBUG level.

This might be true for DataFetcherExceptionResolverAdapter usage, but when we use annotated controllers with @GraphQlExceptionHandler, we see only this log:

2024-06-14 09:05:50.827 [http-nio-auto-1-exec-1] DEBUG o.s.g.d.m.a.s.AnnotatedControllerExceptionResolver - Handling exception with public java.util.List<graphql.GraphQLError> com.xxx.xxx.xxx.exception.GlobalExceptionHandler.handleValidationException(com.xxx.xxx.xxx.xxx.exception.ValidationException,graphql.schema.DataFetchingEnvironment)

I'd expect also AnnotatedControllerExceptionResolver to log resolved exceptions on debug level, not only their "handling"

Metadata

Metadata

Assignees

Labels

status: backportedAn issue that has been backported to maintenance branchestype: bugA general bug

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions