Skip to content

Commit

Permalink
Remove ambiguity/contradiction in SpanContext spec. (open-telemetry#244)
Browse files Browse the repository at this point in the history
Signed-off-by: Christian Neumüller <[email protected]>
  • Loading branch information
Oberon00 authored and bogdandrutu committed Sep 9, 2019
1 parent 14d15ff commit e212bf3
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions specification/api-tracing.md
Original file line number Diff line number Diff line change
Expand Up @@ -167,9 +167,7 @@ propagated along side of a distributed context. `SpanContext`s are immutable.
The OpenTelemetry `SpanContext` representation conforms to the [w3c TraceContext
specification](https://www.w3.org/TR/trace-context/). It contains two
identifiers - a `TraceId` and a `SpanId` - along with a set of common
`TraceFlags` and system-specific `TraceState` values. `SpanContext` is
represented as an interface, in order to be serializable into a wider variety of
trace context wire formats.
`TraceFlags` and system-specific `TraceState` values.

`TraceId` A valid trace identifier is a 16-byte array with at least one
non-zero byte.
Expand Down

0 comments on commit e212bf3

Please sign in to comment.