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: 
  [width="100%",cols="2,5,^1,2",options="header"]
  |===
  | Name | Description | Default | Type
  | *camel.zipkin.client-service-mappings* | Sets client service mapping(s) that matches Camel events to the given zipkin service name. The key is the pattern, the value is the service name. |  | Map
  | *camel.zipkin.endpoint* | Sets the POST URL for zipkin's <a href="http://zipkin.io/zipkin-api/#/">v2 api</a>, usually "\http://zipkinhost:9411/api/v2/spans" |  | String
  | *camel.zipkin.exclude-patterns* | Sets exclude pattern(s) that will disable tracing with zipkin for Camel messages that matches the pattern. |  | Set
  | *camel.zipkin.host-name* | Sets the hostname if sending spans to a remote zipkin scribe (thrift RPC) collector. |  | String
  | *camel.zipkin.include-message-body* | 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 camel.springboot.log-debug-max-chars option. | false | Boolean
  | *camel.zipkin.include-message-body-streams* | Whether to include message bodies that are stream based in the zipkin traces. This is not recommended for production usage, or when having big payloads. You can limit the size by configuring camel.springboot.log-debug-max-chars option. | false | Boolean
  | *camel.zipkin.port* | Sets the port if sending spans to a remote zipkin scribe (thrift RPC) collector. | 0 | Integer
  | *camel.zipkin.rate* | 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%). | 1 | Float
  | *camel.zipkin.server-service-mappings* | Sets server service mapping(s) that matches Camel events to the given zipkin service name. The key is the pattern, the value is the service name. |  | Map
  | *camel.zipkin.service-name* | To use a global service name that matches all Camel events |  | String
  |===
  // spring-boot-auto-configure options: END
  
  
negative.code: zipkin.addClientServiceMapping("http:someserver/somepath", "http:someserver/somepath");
  ----
  
  This is not a recommended approach, but gets you up and running quickly without doing any service name mappings.
  However, when you have multiple systems across your infrastructure, then you should consider using human-readable service names, that you map to instead of using the camel endpoint uris.
  
  [[camel-zipkin-CustomTags]]
  == Custom Tags
  
  If you need to send custom tags to Zipkin server, add an exchange property with name "camel.client.customtags" and value as a Map of your custom tags.
  Refrain from adding too many custom tags in production environment.
  
  Following is one example of how custom tags can be added:
  
  