trace-context
trace-context copied to clipboard
w3c
Trace Context
Filing this based on the discussion in the W3C DT working group meeting. Autopublishing level2/Level3 specs need to work with multiple markdown files. I don't have the complete context, but...
When looking at generated pull request previews and diffs from respec, they are not working because we use the markdown include (https://respec.org/docs/#external-includes) which fails because the browser cannot find the...
This is a first draft of the server-timing response header. It is not meant to be a final version, but a place to start discussion. It is mostly a direct...
Following up on https://github.com/w3c/trace-context/pull/560 The possible alternative for naming would be: instead of: ``` server-timing: trace;tid=0af7651916cd43dd8448eb211c80319c,cid=b7ad6b7169203331 ``` use ``` server-timing: span;id=b7ad6b7169203331,tid=0af7651916cd43dd8448eb211c80319c ``` Benefits: 1. It is already clear that the...
Related to #69, I would like to reopen the discussion around the header name for the client propagation of server tracing information. The current state of the art among practitioners...
Currently, it is not mentioned that the random part of the trace ID (when the random flag is set) should be uniformly distributed. Compare https://w3c.github.io/trace-context/#trace-id, https://w3c.github.io/trace-context/#random-trace-id-flag, and https://w3c.github.io/trace-context/#randomness-of-trace-id. To be...
