sentry-java

sentry-java copied to clipboard

Description

While debugging our spans, we noticed that when a breakpoint is hit, e.g. in a Spring Controller which uses another @Service that is also annotated with @SentrySpan, the debugging causes our span advice to kick in and record a span with op Object.toString.

We're not sure how to fix this without removing functionality like tracking toString() invocations. Maybe it's possible to check if toString (or any other method) is actually being invoked on Object and filter it out.