Thread pool plugin creates extra endpoint

[xiongxoy]

When I use apm-jdk-threadpool-plugin-9.5.0, the plugin creates many endpoints for new threads, but the real endpoint should be SpringScheduled/jobName

How should I pass the tracing context between threads without creating a new endpoint?

[xiongxoy]

I think trace-ignore plugin might help, but is there a way to solve this without using trace-ignore plugin?

[wu-sheng]

How should I pass the tracing context between threads without creating a new endpoint?

If there is no endpoint created, it can't be query unless you have a trace ID. We can't tell how you want to use this after all. x-threadd scenario is variable, people in other case want this.

[xiongxoy]

https://github.com/apache/skywalking-java/blob/aee6f46cbfb32ac489e738f9172848ba3a3c238f/apm-application-toolkit/apm-toolkit-trace/src/main/java/org/apache/skywalking/apm/toolkit/trace/Tracer.java#L22

I think this API of apm-toolkit-trace could be useful if someone doesn't want to create extra endpoint.
One can pass the ContextSnapshotRef on java application side, and do not create a new endpoint or span.
Just an idea, I will try it when I have time.

[xiongxoy]

https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-tracer/