即使在Bluemix中作为报头传递给服务请求，也会重新生成Sleuth报头X-B3-TraceId值

Question

我希望我的服务使用者将TraceId作为标题参数传递，名为X-B3-TraceId和有效的128位十六进制字符串，这些字符串将在行下的进一步路径中传播，实际上服务将返回相同的Sleuth跟踪Id给调用者。我使用了Spring Cloud Sleuth，添加了自定义过滤器和Span提取器，以便在服务响应中投入。

当应用程序部署在嵌入式tomcat中时，整个设置在my local中运行良好，然而，当相同的应用程序部署在Bluemix中时，响应不具有请求中传递的相同的Sleuth跟踪Id。

Please Run the Micro Service locally.    
URL: localhost:9090/hello?name=Ram
Header:
    X-B3-TraceId:d61436368bae3c12ce5f844337f3ee52

Service will return:
    HELLORam
    Header:
    Content-Length →8
    Content-Type →text/plain;charset=UTF-8
    Date →Thu, 11 Jan 2018 01:38:48 GMT
    X-Application-Context →application:9090
    X-B3-TraceId →d61436368bae3c12ce5f844337f3ee52

    Note Trace Id is same in RQ and RS.

Deploy Same Service in IBM Bluemix:
    URL: https://sleuth-header-demo.mybluemix.net/hello?name=Ram .
    Header
    X-B3-TraceId:d61436368bae3c12ce5f844337f3ee52

    Response:
       HELLORam
       Header:
       Connection →Keep-Alive
       Content-Type →text/plain;charset=UTF-8
       Date →Thu, 11 Jan 2018 01:38:30 GMT
       Transfer-Encoding →chunked
       X-Application-Context →sleuth-header-demo:bluemix:0
       X-B3-Traceid →b896d05d9f0ae105
       X-Backside-Transport →OK OK
       X-Global-Transaction-ID →2714561407

 See the Trace Id(X-B3-Traceid) got ignore what was present in 
 Request and got Regenerated as b896d05d9f0ae105

Answer 1

您总是需要传递跟踪标头。必须传播所有的X-B3头，以使分布式跟踪正常工作。