anchor.diff:  
   Visualization of what *Span* and *Trace* will look in a system together with the Zipkin annotations:
   
  -image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/docs/src/main/asciidoc/images/trace-id.png[Trace Info propagation]
  +image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/{branch}/docs/src/main/asciidoc/images/trace-id.png[Trace Info propagation]
   
   Each color of a note signifies a span (7 spans - from *A* to *G*). If you have such information in the note:
   
  
positive.code: 
  *Logback setup*
  
  Below you can find an example of a Logback configuration (file named `https://github.com/spring-cloud-samples/sleuth-documentation-apps/blob/master/service1/src/main/resources/logback-spring.xml[logback-spring.xml]`) that:
  
  - logs information from the application in a JSON format to a `build/${spring.application.name}.json` file
  - has commented out two additional appenders - console and standard log file
  
negative.code: http://www.splunk.com/[Splunk] etc. you can order the events that took place. An example of
  Kibana would look like this:
  
  image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/{branch}/docs/src/main/asciidoc/images/kibana.png[Log correlation with Kibana]
  
  If you want to use https://www.elastic.co/guide/en/logstash/current/index.html[Logstash] here is the Grok pattern for Logstash:
  
  