Non-Error Exceptions thrown in spring controllers cause the span error flag to be set.

[Xyaren]

For example if spring throws a NoResourceFoundException this would result in a 404 response, which is totally expected behaviour.
Unfortunately the span is still flaged as an error.

This causes a spam of error-flagged traces even for harmless stituations.
The same applies to custom created Exceptions that are annotated with @ResponseStatus or any spring controller advices that transalte i.e. a EntityNotFoundException into a 204 response.

Example of a 404 causing the span to be tagged as error.

[dgswan]

@Xyaren
We have the same thing in our project. It looks similar to #7288. Please see the answer #7288 (comment).