Btukfyl

I am trying to use the 128 bit Sleuth generated TraceId as a unique identifier for request hitting my controller. I understand that the default traceId is 64 and to change it, I have to add the following to the application.properties:

spring.sleuth.trace-id128=true

This works on my local but when I deploy it to PCF,the trace ID is 64 bits. I have created a sample project that only has a simple controller to demonstrate this.

@RestController

public class Controller {

    private Logger logger = LoggerFactory.getLogger(Controller.class);

    @Autowired

    private Tracer tracer;

    @GetMapping("/")

    public void test(){

        logger.info("LOGGED +["+tracer.currentSpan().context().traceIdString()+"]");

    }

}

In my local, it will print:

com.example.demo.Controller: LOGGED + [5bfcb33c9d564481479f2c212ec08143]

In PCF, it prints:

om.example.demo.Controller : LOGGED + [97a1168857dc7088]

Is PCF overwriting this configuration?

Updates

Included "X-B3-TraceId" and "X-B3-SpanId" in my request and the traceId is now 128bit but not the same string as what was passed in the request header.

Details from log

It's possible that PCF, more specifically the Gorouter, is creating the trace id and that is getting propagated onto your app, which instead of creating a new 128-bit trace id is reusing the existing 64-bit trace id.

PCF has support for Zipkin Tracing and this is enabled by default, so it's on in most environments.

https://docs.pivotal.io/pivotalcf/2-3/adminguide/zipkin_tracing.html

According to the docs, the Gorouter will check for the existence of Zipkin headers on incoming requests and if they are not present will create them.

If the X-B3-TraceId and X-B3-SpanId HTTP headers are not present in the request, the Gorouter generates values for these and inserts the headers into the request forwarded to an application.

and

If the X-B3-TraceId and X-B3-SpanId HTTP headers are present in the request, the Gorouter forwards them unmodified.

https://docs.pivotal.io/pivotalcf/2-3/concepts/http-routing.html#zipkin-headers

You can see here that it's creating a 64-bit trace id.

https://github.com/cloudfoundry/gorouter/blob/master/handlers/zipkin.go#L49-L57

You could confirm by sending a request with the headers X-B3-TraceId and X-B3-SpanId set. In this case Gorouter should forward them along unmodified.

Ex: curl -v -H 'X-B3-TraceId: 5bfcb33c9d564481479f2c212ec08143' -H X-B3-SpanId: 5bfcb33c9d564481479f2c212ec08143' https://your-cool-app.com/test.