anchor.diff:  zipkin.init(camelContext);
   ----
   
  -The configuration above will trace all incoming and outgoing
  -messages in Camel routes. 
  -
  -To use ZipkinTracer in XML, all you need to do is to define scribe and
  -zipkin tracer beans. Camel will automatically discover and use them.
  +The configuration above will trace all incoming and outgoing messages in Camel routes. 
  +
  +To use ZipkinTracer in XML, all you need to do is to define scribe and zipkin tracer beans.
  +Camel will automatically discover and use them.
   
   [source,xml]
   ----
  
positive.code: 
  *Available as of Camel 2.18*
  
  The Camel Zipkin component is used for tracing and timing incoming and
  outgoing Camel messages using http://zipkin.io/[zipkin].
  
  Events (span) are captured for incoming and outgoing messages being sent
  to/from Camel.
  
  This means you need to configure which Camel endpoints map
  to zipkin service names.
  
  The mapping can be configured using:
  
  * route id - A Camel route id
  * endpoint url - A Camel endpoint url
  
  For both kinds you can match using wildcards and regular expressions,
  using the rules from Intercept.
  
  To match all Camel messages you can use * in the pattern and configure
  that to the same service name.
  
  If no mapping has been configured, Camel will fallback and use
  endpoint uri's as service names.  +
  However, it's recommended to configure service mappings so you can use
  human-readable names instead of Camel endpoint uris in the names.
  
  Camel will auto-configure a span reporter one hasn't been explicitly configured,
  and if the hostname and port to a zipkin collector has been configured as environment variables
  
  * ZIPKIN_COLLECTOR_HTTP_SERVICE_HOST - The http hostname
  * ZIPKIN_COLLECTOR_HTTP_SERVICE_PORT - The port number
  
negative.code: * ZIPKIN_COLLECTOR_THRIFT_SERVICE_HOST - The Scribe (Thrift RPC) hostname
  * ZIPKIN_COLLECTOR_THRIFT_SERVICE_PORT - The port number
  
  This makes it easy to use camel-zipkin in container platforms where the platform can run your application in a linux container where service configurations are provided as environment variables.
  
  [[camel-zipkin-Options]]
  == Options
  
  [width="100%",cols="10%,10%,80%",options="header",]
  |===
  |Option 
  |Default 
  |Description
  
  |rate 
  |1.0f 
  |Configures a rate that decides how many events should be traced by zipkin.
  The rate is expressed as a percentage (1.0f = 100%, 0.5f is 50%, 0.1f is 10%).
  
  |spanReporter 
  |  
  |*Mandatory:* The reporter to use for sending zipkin span events to the zipkin server.
  
  |serviceName 
  |  
  | To use a global service name that matches all Camel events
  
  |clientServiceMappings 
  |  
  | Sets the *client* service mappings that matches Camel events to the given zipkin service name.
  The content is a `Map<String, String>` where the key is a pattern and the value is the service name.
  The pattern uses the rules from Intercept.
  
  |serverServiceMappings 
  |  
  | Sets the *server* service mappings that matches Camel events to the given zipkin service name.
  The content is a `Map<String, String>` where the key is a pattern and the value is the service name.
  The pattern uses the rules from Intercept.
  
  |excludePatterns 
  |  
  | Sets exclude pattern(s) that will disable tracing with zipkin for Camel messages that matches the pattern.
  The content is a `Set<String>` where the key is a pattern.
  The pattern uses the rules from Intercept.
  
  |includeMessageBody 
  |false 
  |Whether to include the Camel message body in the zipkin traces.
  This is not recommended for production usage, or when having big payloads.
  You can limit the size by configuring the xref:manual::faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
  debug log size]. 
  
  |includeMessageBodyStreams 
  |false 
  |Whether to include message bodies that are stream based in the zipkin traces.
  This requires enabling streamcaching on the routes or globally on the `CamelContext`.
  This is not recommended for production usage, or when having big payloads.
  You can limit the size by configuring the xref:manual::faq/how-do-i-set-the-max-chars-when-debug-logging-messages-in-camel.adoc[max
  debug log size].  
  
  |===
  
  // spring-boot-auto-configure options: START
  