anchor.diff:  
   include::./attributes.adoc[]
   
  -This guide explains how your Quarkus application can utilize opentracing to provide distributed tracing for
  +This guide explains how your Quarkus application can utilize OpenTracing to provide distributed tracing for
   interactive web applications.
   
   == Prerequisites
  
positive.code: quarkus.jaeger.service-name=myservice // <1>
  quarkus.jaeger.sampler-type=const // <2>
  quarkus.jaeger.sampler-param=1 // <3>
  ----
  
  <1> If the `quarkus.jaeger.service-name` property (or `JAEGER_SERVICE_NAME` environment variable) is not provided then a "no-op" tracer will be configured, resulting in no tracing data being reported to the backend.
  <2> Setup a sampler, that uses a constant sampling strategy.
  <3> Sample all requests. Set sampler-param to somewhere between 0 and 1, e.g. 0.50, if you do not wish to sample all requests.
  
  The second approach is to supply the properties as https://www.jaegertracing.io/docs/latest/client-features/[environment variables]. These can be specified as `jvm.args` as shown in the following section.
  
  
negative.code: import javax.ws.rs.Path;
  import javax.ws.rs.Produces;
  import javax.ws.rs.core.MediaType;
  import org.jboss.logging.Logger;
  
  @Path("/hello")
  public class TracedResource {
  
      private static final Logger LOG = Logger.getLogger(TracedResource.class);
  
      @GET
      @Produces(MediaType.TEXT_PLAIN)
      public String hello() {
          LOG.info("hello");
          return "hello";
      }
  }
  