tool.ren

Trace Context & Baggage Debugger

Parse traceparent, tracestate and baggage, recognize B3 and Jaeger context, validate formats, simulate multiple hops, and generate injection code.

Headers are parsed locally and sensitive baggage is masked
Trace IDs, parent IDs, tracestate, baggage and header contents never enter anonymous analytics.

Headers and propagation settings

Input is limited to 64 KiB. Raw headers, cURL and JSON objects are supported.

Load a sample, paste headers or generate a root context

Each field, a propagation simulation and copyable code will appear here.

B3 and Jaeger conversion is a general preview. Validate vendor sampling, debug flags and tracestate semantics with the corresponding SDK.

About Trace Context & Baggage Debugger

Validate W3C trace headers and simulate cross-service propagation. Parse traceparent, tracestate and baggage, recognize B3 and Jaeger context, validate formats, simulate multiple hops, and generate injection code. The core workflow is designed to run in your current browser.

Key capabilities

  • Strictly check W3C traceparent, tracestate and baggage limits
  • Recognize B3 and Jaeger headers and preview a W3C conversion
  • Preserve the Trace ID while generating a new Parent ID for each hop
  • Generate sanitized header injection examples for six languages

Useful for

  • Investigate broken traces across gateways and microservices
  • Review sampling flags, vendor state and baggage encoding
  • Give propagation examples to client or server teams

Frequently asked questions

Is Trace Context & Baggage Debugger free to use online?

Yes. Trace Context & Baggage Debugger opens in a modern browser and does not require desktop software installation.

What is Trace Context & Baggage Debugger useful for?

Common use cases include Investigate broken traces across gateways and microservices; Review sampling flags, vendor state and baggage encoding.

Is my input or file uploaded?

The core processing workflow is designed to run locally in the browser. Key capabilities include Strictly check W3C traceparent, tracestate and baggage limits, Recognize B3 and Jaeger headers and preview a W3C conversion, Preserve the Trace ID while generating a new Parent ID for each hop; account, comments, and anonymous analytics may still create normal site requests.

Comments

0 comments

Sign in to comment
AAccount

Sign in to comment and reply.

Sign in
No comments yet. Be the first to leave feedback.

ToolRen Online Toolkit © 2026