anchor.diff:  
   Visualization of what *Span* and *Trace* will look in a system together with the Zipkin annotations:
   
  -image::trace-id.png[Trace Info propagation]
  +image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/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: http://www.splunk.com/[Splunk] etc. you can order the events that took place. An example of
  Kibana would look like this:
  
  image::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:
  
  
negative.code: 
  Altogether there are *10 spans* . If you go to traces in Zipkin you will see this number:
  
  image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/docs/src/main/asciidoc/images/zipkin-traces.png[Traces]
  
  However if you pick a particular trace then you will see *7 spans*:
  
  image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-sleuth/master/docs/src/main/asciidoc/images/zipkin-ui.png[Traces Info propagation]
  
  NOTE: When picking a particular trace you will see merged spans. That means that if there were 2 spans sent to
  Zipkin with Server Received and Server Sent / Client Received and Client Sent
  