anchor.diff:  
   Events (span) are captured for incoming and outgoing messages being sent
   to/from Camel.
  -
  -NOTE: camel-zipkin is planned to be refactored in Camel 2.22.0 to not use zipkin-scribe
  -but use the default http transport. This work may cause backwards incompatibility.
   
   This means you need to configure which Camel endpoints map
   to zipkin service names.
  
positive.code: [source,xml]
  ----
    <!-- configure how to reporter spans to a Zipkin collector
            (the dependency is io.zipkin.reporter2:zipkin-reporter-spring-beans) -->
    <bean id="http" class="zipkin2.reporter.beans.AsyncReporterFactoryBean">
      <property name="sender">
        <bean id="sender" class="zipkin2.reporter.beans.OkHttpSenderFactoryBean">
  
negative.code: ----
  ZipkinTracer zipkin = new ZipkinTracer();
  // Configure a reporter, which controls how often spans are sent
  //   (the dependency is org.apache.zipkin.reporter2:zipkin-sender-okhttp3)
  sender = OkHttpSender.create("http://127.0.0.1:9411/api/v2/spans");
  zipkin.setSpanReporter(AsyncReporter.create(sender));
  // and then add zipkin to the CamelContext
  