In the CROSS_THREAD scenario where spanA asynchronously calls spanB, if spanA is ignored, can spanB also be automatically ignored?

[gzlicanyi]

In the CROSS_THREAD scenario where spanA asynchronously calls spanB, if spanA is ignored, can spanB also be automatically ignored?

[wu-sheng]

How could you be possible to ignore a span only? SkyWalking sampling policy is segment oriented.

A span is created before continued(CROSS_THREAD). They are irrelevant. Same story for service A calling service B. Sampling are controlled at both ends.

[wu-sheng]

If this is Spring Cloud gateway, I think you can't do that easily.

[gzlicanyi]

Can I modify it such that if ContextSnapshot isValid() == false when the createLocalSpan() method is called, I set the operationName to null, causing the ContextManager to create an IgnoredTracerContext?

[wu-sheng]

At least you can't do that right now.

[gzlicanyi]

Why? I can submit a PR.

[wu-sheng]

I mean, set the operationName to null to trigger IgnoredTracerContext is not a recommend way. And this will trigger different behavior with other plugins.

If you want to do this, we need to add a mechanism like forceSampling or forceIgnoring mechanism.

[wu-sheng]

Implemented through apache/skywalking-java#689