trace-context
trace-context copied to clipboard
Trace Context
Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service
## Background Starting from the [definition](https://w3c.github.io/trace-context/#design-overview) about the "minimum" interaction: ``` At a minimum they MUST propagate the traceparent and tracestate headers and guarantee traces are not broken. This behavior...
I could not find any information about this. But my understanding is that any header included back to the client in the 304 Not Modified response gets merged with headers...
### Problem SAP would like to encode context information from existing widely-used correlators into tracestate header parts. These correlators use data that is a structured record of raw binary data....
We need to update the privacy section to include information about traceresponse headers.
Per discussion in WG meeting: Update tests to test Trace Context level 2 by default. Level 2 features are optional. Hence, we should likely test level 2 by default but...
Currently (level 1, version specifier `00`), if a trace participant encounters trace flags it does not recognize it is required to set those flags to `0` before forwarding the trace...
Currently, the span id included in the `traceresponse` header is a child-id, and refers to the span-id of server operation. This only enables linking the browser span to the server,...
We are looking to adopt this standard but we are wondering why the traceparent is a single identifier that consists of 2 parts where the parent-id is only 8 bytes....
Hello all, Wanted to get your feedback on the below use case related to tracecontext: Let's say there's a global load balancer service (say, a L7 load balancer offered by...