anchor.diff:  
   `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.
  +`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
  
positive.code: 
  `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 client error (4xx) 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.
  
  === Enabling explicit distributed tracing code instrumentation
  
negative.code: 
  This specification defines an easy way to allow an application running in a
  MicroProfile container to take advantage of distributed tracing by using an
  OpenTracing Tracer implementation. This document and implementations MUST comply with
  OpenTracing specification and semantic conventions if it is not defined otherwise.
  
  There are two operation modes
  
  