Skip to converter

TOML records to Zipkin v2 JSON spans (restricted) Converter.

Convert TOML records to Zipkin v2 JSON spans (restricted) distributed tracing records locally without uploading diagnostic files.

Featured resources

App or project

NGSpeak: Language Learning App

Learn English and Bengali with 160 offline-first lessons across CEFR A1–C2, including speaking, writing, pronunciation practice, and progress tracking.

Download Now

Convert your file

INPUTTOML records
OUTPUTZipkin v2 JSON spans (restricted)
Files stay on your device

Up to 2 MiB · 1–1,000 spans · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert TOML records to Zipkin v2 JSON spans (restricted)

  1. Choose a source file. Select a real TOML records file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated Zipkin v2 JSON spans (restricted) file. Your original file is unchanged.

FORMAT GUIDE

Why convert TOML records to Zipkin v2 JSON spans (restricted)?

Review span timing, service names and parent relationships in a spreadsheet or compatible tracing format.

  • Reviewing trace timings in spreadsheets.
  • Exchanging small span-only trace reports between supported tools.
  • Analyzing service spans without uploading private trace data.

UNDERSTAND YOUR FILES

TOML records vs. Zipkin v2 JSON spans (restricted): what changes?

Input · TOML records

TOML stores structured settings and values. These tools support simple repeated record tables with text values, not arbitrary configuration documents.

Output · Zipkin v2 JSON spans (restricted)

Review span timing, service names and parent relationships in a spreadsheet or compatible tracing format. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Before you share the output

Check column headings, escaped characters, delimiters and empty values. Data type information and spreadsheet formulas may not survive a plain-text format change.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

Supports 1–1,000 complete, span-only tracing records. Table headings, in order: trace_id, span_id, parent_id, service, operation, start_us, duration_us. Trace IDs are 16/32 lowercase hex digits; span and parent IDs are 16 hex digits. Timestamp and duration are positive microsecond integers within JavaScript safe-integer range; service names are safe lowercase ASCII, and operation text supports Unicode including Bengali. Supports a strict subset of Zipkin v2 JSON arrays and Jaeger query JSON traces. Remote endpoint details, span kind, annotations, tags, process tags, logs, warnings, exception data, sampling flags, links and unrecognized vendor metadata cannot be transferred, so inputs containing them are rejected. This exchanges existing trace records; it does not instrument applications, run traces, send telemetry or preserve every trace schema feature.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

TOML records to Zipkin v2 JSON spans (restricted) questions

Does the tool capture or send live telemetry?

No. It only converts a local file you select.

What spreadsheet columns must I use?

trace_id, span_id, parent_id, service, operation, start_us, duration_us, in that order.

Does it support full Jaeger and Zipkin exports?

No. Supports 1–1,000 complete, span-only tracing records. Table headings, in order: trace_id, span_id, parent_id, service, operation, start_us, duration_us. Trace IDs are 16/32 lowercase hex digits; span and parent IDs are 16 hex digits. Timestamp and duration are positive microsecond integers within JavaScript safe-integer range; service names are safe lowercase ASCII, and operation text supports Unicode including Bengali. Supports a strict subset of Zipkin v2 JSON arrays and Jaeger query JSON traces. Remote endpoint details, span kind, annotations, tags, process tags, logs, warnings, exception data, sampling flags, links and unrecognized vendor metadata cannot be transferred, so inputs containing them are rejected. This exchanges existing trace records; it does not instrument applications, run traces, send telemetry or preserve every trace schema feature.