traceparent, tracestate and B3 decoder
Paste tracing headers from a request (as name: value lines) or a single value. The page decodes them, flags what a receiver would reject and converts between W3C Trace Context and Zipkin B3. It also warns when two propagation formats in one request carry different trace IDs, a common reason for traces that break at a gateway. Runs in your browser; we only count anonymous visits.
How to use this tool
- Copy the tracing headers from your logs, browser developer tools or a gateway trace and paste them.
- Read the findings: red items are invalid and receivers will usually ignore the header and start a new trace.
- Use the converted values to test how a gateway or service that only understands the other format behaves.
Example
The pre-filled headers carry two different trace IDs, one in traceparent and one in b3. This is what happens when a proxy adds a header of its own format and the downstream service reads the other one: the trace splits in two. Fix the b3 line to 0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-1 and the warning disappears.
Limits
The checks follow the W3C Trace Context and Zipkin B3 propagation specifications. A 64-bit B3 trace ID is padded with zeros to 128 bits when converted to W3C; some tracing systems do this differently. The decoder checks syntax, not whether a trace exists in your tracing backend. Be careful with vendor entries in tracestate: they can contain account identifiers.
Privacy and security of what you enter
Everything is decoded in your browser. Nothing is uploaded. See the privacy notice.
We configure and review API gateways, including WSO2 and tracing propagation. See the services or the API hardening checklist.
Message us on LinkedIn