Dubbo: don't create spans for calls inside the same jvm #7761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #7520
Invoking a dubbo service, like in https://github.com/zewade/opentelemetry-dubbo-demo/blob/d7e2417ae787808dbfb43747d586b91a1b29ecec/demo-business-provider/src/main/java/cn/zewade/business/controller/BusinessController.java#L20, creates a client span (and a server span on the receiving end). If the caller and service are on the jvm this call doesn't go through remoting and will be handled with regular java calls. Now when the initially called service calls another service, like in https://github.com/zewade/opentelemetry-dubbo-demo/blob/main/demo-business-provider/src/main/java/cn/zewade/business/dubbo/BusinessDubboServiceImpl.java#L25, that second call will also attempt to create a client span. This second client span will be suppressed which will also suppress context propagation.