anchor.diff:  Spring Cloud GCP Trace does override some Sleuth configurations:
   
   - Always uses 128-bit Trace IDs. This is required by Stackdriver Trace.
  -- Does not use Span joins. Span joins will share the span ID between the client and server Spans. Stackdriver requires that every Span ID within a Trace to be unique, so Span joins are not supported.
  +- Does not use Span joins.
  +Span joins will share the span ID between the client and server Spans.
  +Stackdriver requires that every Span ID within a Trace to be unique, so Span joins are not supported.
   - Uses `StackdriverHttpClientParser` and `StackdriverHttpServerParser` by default to populate Stackdriver related fields.
   
   === Integration with Logging
  
positive.code: If the Trace integration is used together with the Logging one, the request logs will be associated to the corresponding traces.
  The trace logs can be viewed by going to the https://console.cloud.google.com/traces/traces[Google Cloud Console Trace List], selecting a trace and pressing the `Logs -> View` link in the `Details` section.
  
  
  === Sample
  
  A https://github.com/spring-cloud/spring-cloud-gcp/tree/master/spring-cloud-gcp-samples/spring-cloud-gcp-trace-sample[sample application] and a https://codelabs.developers.google.com/codelabs/cloud-spring-cloud-gcp-trace/index.html[codelab] are available.
  
negative.code: == Spring Cloud Sleuth
  
  https://cloud.spring.io/spring-cloud-sleuth/[Spring Cloud Sleuth] is an instrumentation framework for Spring Boot applications.
  It captures trace information and can forward traces to services like Zipkin for storage and analysis.
  
  Google Cloud Platform provides its own managed distributed tracing service called https://cloud.google.com/trace/[Stackdriver Trace].
  Instead of running and maintaining your own Zipkin instance and storage, you can use Stackdriver Trace to store traces, view trace details, generate latency distributions graphs, and generate performance regression reports.
  