traqo-tracing
Installation
SKILL.md
traqo Trace Analysis
Analyze JSONL traces produced by the traqo Python package.
Trace File Structure
Traces are stored as compressed .jsonl.gz files, optionally with a .content.jsonl.zst sidecar for externalized large span inputs. The raw .jsonl buffer is deleted after compression. Last line is always trace_end with summary stats. Start there.
For compressed traces, large span_start inputs (>10 KB) are replaced with {"_ref": "<span_id>", "_size": N} stubs. The full input lives in the companion .content.jsonl.zst file. If you see a _ref stub, use traqo ui (loads on click) or the Python read_content() API to retrieve the original input.
Event Types
| Event | Key Fields |
|---|---|
trace_start |
tracer_version, input, metadata, tags, thread_id |
span_start |
id, parent_id, name, input, metadata, tags, kind |
span_end |
id, parent_id, name, duration_s, status, output, metadata, tags, kind |
event |
name, data (arbitrary dict) |
trace_end |
duration_s, output, stats, children |