Traces are designed to show the flow of execution.


  • Context about the position is propagated through tracing headers.
    • The preferred specification for context propagation in HTTP is W3C Trace Context, though B3 (Zipkin) is supported.
  • Spans represent individual calls or transactions in a trace.
    • Kind identifies their type:
      • client/server
      • producer/consumer
      • internal
    • Attributes contain arbitrary metadata.
    • Events are named strings.
    • Links may help identify background/batch jobs related to a given transaction.