Xybrid

xybrid trace

Analyze an explicitly exported OTLP trace artifact

xybrid trace FILE summarizes an OTLP/JSON artifact created by xybrid run --trace-export FILE. Capture belongs to that run; traces are not saved automatically to a session directory.

Usage

xybrid run --model kokoro-82m --input-text "Hello" --trace-export trace.json
xybrid trace trace.json
xybrid trace trace.json --export summary.json
ArgumentDescription
FILERequired path to an OTLP/JSON trace artifact
--export PATHAlso write the analysis summary to this file

The command prints a JSON summary with operation counts, logical token usage and an operations array. Each operation includes its trace/span IDs, parent, duration, model, location, route, load trigger, error classification and any available usage or timing. Unavailable measurements remain null. Concrete attempt usage is retained on the attempt and excluded from logical totals, so a retry does not count the same logical request twice.

Local capture and remote export

xybrid run --trace renders the current run's local trace. Add --trace-export PATH to write its OTLP/JSON artifact. Neither flag enables remote export; configure --observability or Collector environment variables separately. OTEL_SDK_DISABLED=true disables remote export while keeping local capture available.

Artifacts may contain application data. The analyzer's summary selects operation metadata and measurements; it does not copy governed prompt/output content into its summary.

Migration

Replace xybrid trace --latest or --session ID with an explicit artifact path. Legacy session logs and Chrome trace files are not accepted. Use xybrid run ... --trace-export FILE when creating new captures.

On this page