We are seeing examples where Spring Scheduling INTERNAL spans are created inside of an existing parent span, which creates unnecessary noise. And these spans don't necessary make sense as these are not "background jobs" (since they occur inside of an existing span). (see for example https://github.com/microsoft/ApplicationInsights-Java/issues/2870) This PR changes Spring Scheduling instrumentation to only instrumenting repeating jobs, not one-time scheduled jobs (which corresponds to ScheduledExecutorService behavior where context is not propagated to runnable) --------- Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com> |
||
---|---|---|
.. | ||
bootstrap | ||
javaagent |