w3c/trace-context

Issues

• Clarify tracestate keys MUST be unique

  #446 opened 3 years ago
  31

• Move response header Returning the traceresponse Field to non-normative processing section.

  #445 opened 4 years ago
  0

• term `negative sampling decision` may not be very clear to a reader

  #444 opened 3 years ago
  0

• Expected behavior with regard to starting a trace should be spelled out explicitly

  #442 opened 3 years ago
  2

• Should a tracestate key always be allowed to start with a lowercase letter or digit?

  #441 opened 4 years ago
  2

• How should tracestate list members be truncated when they exceed 32?

  #440 opened 4 years ago
  1

• Clarify how tracestate can or cannot be used by application developers

  #439 opened 3 years ago
  2

• How to preserve trace context on http redirect ?

  #438 opened 4 years ago
  11

• Encourage traceresponse to be provided even when traceparent is used

  #437 opened 4 years ago
  5

• Erratum level-1: Contradiction in TraceState

  #428 opened 4 years ago
  1

• Backport #423 to `level-1`

  #424 opened 4 years ago
  1

• Contradiction in TraceState requirements

  #422 opened 4 years ago
  4

• Fix key errors in test suite

  #416 opened 4 years ago
  1

• What's the recommended guideline for generating parent-id?

  #412 opened 4 years ago
  5

• Document rationale for 255 leading spaces in tracestate values or remove it

  #409 opened 4 years ago
  7

• Clarify use of trace-id in response header

  #407 opened 4 years ago
  3

• Remove proposed-parent-id from response header

  #406 opened 4 years ago
  7

• Requirements for CORS safe-list

  #405 opened 5 years ago
  3

• Fix numbering/level in rendered spec

  #403 opened 4 years ago
  0

• Make initial traceparent optional

  #401 opened 5 years ago
  5

• [response header] Representing optional fields

  #400 opened 4 years ago
  1

• [response header] Representing server span ID vs proposed parent ID

  #399 opened 5 years ago
  6

• Should response header fields be optional?

  #398 opened 3 years ago
  11

• Be consistent with normative / non-normative sections

  #396 opened 5 years ago
  2

• Can the intelligence-free nature of ids be confirmed or audited by external parties?

  #394 opened 3 years ago
  11

• Privacy: What information may be revealed?

  #393 opened 5 years ago
  2

• Define the intended implementer

  #392 opened 5 years ago
  3

• Bogus trace and parent IDs when not sampling

  #390 opened 4 years ago
  3

• W3C Trace Context only support HTTP protocol？

  #389 opened 5 years ago
  1

• Stop using vendor terminology

  #387 opened 5 years ago
  1

• Should span annotations be supported?

  #385 opened 5 years ago
  3

• Discourage vendors from validating other vendors' tracestate entries

  #384 opened 5 years ago
  4

• Clarify the requirements of short `trace-id` in section 8.4

  #379 opened 5 years ago
  7

• Remove duplicate "the" in section 8.4

  #378 opened 5 years ago
  0

• Test report?

  #373 opened 5 years ago
  5

• Response header name

  #371 opened 5 years ago
  5

• Clarify handling of duplicate keys in tracestate

  #369 opened 3 years ago
  7

• Fix grammar in higher-version flags parsing

  #368 opened 5 years ago
  0

• Use consistent notation in section 3.2.2.1

  #367 opened 5 years ago
  0

• Test suite server crashes with newer multidict version

  #366 opened 4 years ago
  1

• ABNF improvement

  #364 opened 3 years ago
  7

• Unused file in spec directory

  #363 opened 5 years ago
  0

• Create a first draft of a response header spec

  #361 opened 5 years ago
  1

• Add general text format to the next version of the spec

  #360 opened 5 years ago
  0

• We mention in joint blog post that opentelemetry is a reference implementation while readme says opencensus

  #353 opened 5 years ago
  2

• ReSpec issue

  #352 opened 5 years ago
  1

• Inter-operability of tracing systems operating with shorter trace-id

  #349 opened 5 years ago
  16

• Clarify "opaque"

  #348 opened 4 years ago
  2

• Wording in 4.2.2 is unclear

  #347 opened 5 years ago
  0

• Warning message against implementation

  #345 opened 5 years ago
  2