anchor.diff:  This is particularly important in a microservices environment where a request typically flows through multiple services.
   To accomplish distributed tracing, each service must be instrumented to log messages with a correlation id that may have been propagated from an upstream service.
   A common companion to distributed trace logging is a service where the distributed trace records can be stored.
  -See also http://opentracing.io/documentation/pages/supported-tracers.html[Examples on opentracing.io].
  +See also examples on http://opentracing.io/documentation/pages/supported-tracers.html[opentracing.io].
   The storage service for distributed trace records can provide features to view the cross service trace records associated with particular request flows.
   
   It will be useful for services written in the MicroProfile framework to be able to integrate well with a distributed trace system that is part of the larger microservices environment.
  
positive.code: ===== Server Span tags
  Spans created for incoming requests will have the following tags added by default:
  
  * Tags.SPAN_KIND = Tags.SPAN_KIND_SERVER
  * Tags.HTTP_METHOD
  * Tags.HTTP_URL
  * Tags.HTTP_STATUS
  * Tags.ERROR (if true)
  
  Tags.SPAN_KIND MUST be specified at Span start time.
  
  An https://github.com/opentracing/specification/blob/master/semantic_conventions.md[Tags.ERROR tag] SHOULD be added to a Span on failed operations for any server error (5xx) codes.
  If there is an exception object available the implementation SHOULD also add logs `event=error` and `error.object=<error object instance>` to the active span.
  
  ==== Span creation and injection for outbound requests
  When a request is sent from a JAX-RS javax.ws.rs.client.Client, a new Span is created and its SpanContext is injected in the outbound request for propagation downstream. The new Span will be a child of the active Span if an active Span exists. The new Span will be finished when the outbound request is completed.
  
  ===== Client Span name
  The default operation name of the new Span for the outgoing request is
  
negative.code: 
  The `@Traced` annotation has two optional arguments.
  
  * `value=[true|false]`. Defaults to true.
  If `@Traced` is specified at the class level, then `@Traced(false)` is used to annotate specific methods to disable creation of a Span for those methods.
  By default all JAX-RS endpoint methods are traced.
  To disable Span creation of a specific JAX-RS endpoint, the `@Traced(false)` annotation can be used.
  +
  When the `@Traced(false)` annotation is used for a JAX-RS endpoint method, the upstream SpanContext will not be extracted. Any Spans created, either automatically for outbound requests, or explicitly using an injected Tracer, will not have an upstream parent Span in the Span hierarchy.
  
  * `operationName=<Name for the Span>`.
  Default is `""`.
  If the `@Traced` annotation finds the operationName as `""`, the default operation name is used. For a JAX-RS endpoint method (see <<server-span-name>>).
  If the annotated method is not a JAX-RS endpoint, the default operation name of the new Span for the method is
  ```
  <package name>.<class name>.<method name>
  