(servicecomb-docs) branch java-chassis-2.x updated: update docs of microservice-invocation-chain (#303)

[li...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

liubao pushed a commit to branch java-chassis-2.x
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git


The following commit(s) were added to refs/heads/java-chassis-2.x by this push:
     new 82c9c51  update docs of microservice-invocation-chain (#303)
82c9c51 is described below

commit 82c9c51cd20a9f056e04aba5b612bc8c95507480
Author: yanghao <73...@users.noreply.github.com>
AuthorDate: Mon Dec 4 08:58:33 2023 +0800

    update docs of microservice-invocation-chain (#303)
---
 .../microservice-invocation-chain.md                  | 19 +++++++++++++++++++
 .../microservice-invocation-chain.md                  | 18 ++++++++++++++++++
 2 files changed, 37 insertions(+)

diff --git a/java-chassis-reference/en_US/docs/general-development/microservice-invocation-chain.md b/java-chassis-reference/en_US/docs/general-development/microservice-invocation-chain.md
index 5e9193a..0d6bcf6 100644
--- a/java-chassis-reference/en_US/docs/general-development/microservice-invocation-chain.md
+++ b/java-chassis-reference/en_US/docs/general-development/microservice-invocation-chain.md
@@ -57,3 +57,22 @@ Set the tracking processor and data collection service address in the microservi
 In this way, with the addition of two configuration items and no changes to one line of code, we started the distributed call chain tracking function based on Zipkin and Java chassis.
 
 **Note **If other dependencies in the project also introduce a zipkin (such as Spring Cloud), which may cause the zipkin version to be inconsistent and run incorrectly, you need to declare the zipkin version in the project pom.
+
+### Providing the full http.path
+
+The default http.path returned by Java Chassis is the operation path, which is different from the path of other frameworks. You can return the full http.path as follows.
+
+Setting the value of servicecomb.tracing.workWithThirdParty to true in the file of micoservice.yaml.
+
+```
+  servicecomb: 
+    handler: 
+      chain: 
+        Consumer: 
+          default: loadbalance,tracing-consumer
+        Provider: 
+          default: tracing-provider
+    tracing:
+      workWithThirdParty: true
+```
+
diff --git a/java-chassis-reference/zh_CN/docs/general-development/microservice-invocation-chain.md b/java-chassis-reference/zh_CN/docs/general-development/microservice-invocation-chain.md
index ce2301c..32945e2 100644
--- a/java-chassis-reference/zh_CN/docs/general-development/microservice-invocation-chain.md
+++ b/java-chassis-reference/zh_CN/docs/general-development/microservice-invocation-chain.md
@@ -58,5 +58,23 @@ ServiceComb 集成了 Zipkin 提供自动调用链追踪能力，如此一来用
 
 **注意 **如果项目中的其他依赖也引入了 zipkin （例如 Spring Cloud），可能导致 zipkin 版本不一致而运行出错，这时需要在项目 pom 中声明 zipkin 版本。
 
+### 提供完整的http.path
+
+由于Java Chassis中默认返回的http.path是operation路径，相较于其他框架的路径区别较大，可以通过下述方式，返回完整的http.path
+
+在microservice.yaml文件中设置配置项：servicecomb.tracing.workWithThirdParty的值为true
+
+```
+  servicecomb: 
+    handler: 
+      chain: 
+        Consumer: 
+          default: loadbalance,tracing-consumer
+        Provider: 
+          default: tracing-provider
+    tracing:
+      workWithThirdParty: true
+```
+