Actual class names of spring boot application are wrapped by SpringSchedulingRunnablewrapper

[vasireddy99]

Describe the bug
When using OTEL with Spring boot app, spring boot admin console wraps all actual classes with io.opentelemetry.javaagent.instrumentation.spring.scheduling.SpringSchedulingRunnablewrapper.

What did you expect to see?
It is expected to to see the actual classes and not to have the above wrapper as shown in the image.

What version are you using?
v1.14.0

[breedx-splk]

Hi @vasireddy99 . The way that the Spring Scheduling instrumentation works is by wrapping Runnable instances with instrumentation code (in order to do tracing things, like create timed spans etc). It's unfortunate that Spring doesn't provide a more flexible instrumentation hook for this stuff, so this is what we kinda have to do. As a result, the Spring task runners only see the instrumentation classes.

If the Spring Scheduling instrumentation is getting in the way and causing problems, you should be able to disable it by passing -Dotel.instrumentation.spring-scheduling-3.1.enabled=false to the JVM.

[laurit]

As @breedx-splk mentioned this is because we wrap the Runnable instances passed to the constructor of org.springframework.scheduling.config.Task. To fix this we could try wrapping it at some later point, perhaps when any of the schedule methods are called on org.springframework.scheduling.TaskScheduler?

[breedx-splk]

[...]we could try wrapping it at some later point, perhaps when any of the schedule methods are called on org.springframework.scheduling.TaskScheduler?

If that list in the screenshot is created within the schedule methods, though, the same problem would exist right?

[laurit]

[...]we could try wrapping it at some later point, perhaps when any of the schedule methods are called on org.springframework.scheduling.TaskScheduler?

If that list in the screenshot is created within the schedule methods, though, the same problem would exist right?

Yes, but I find it unlikely that it is filled there.