Jaeger Trace Compare

Use this skill when you need reproducible performance comparison from Jaeger traces between two code versions.

Prerequisites

• Jaeger is running (just jaeger-up)
• Traces are generated with OTEL_EXPORTER_OTLP_ENDPOINT set
• git.commit resource attribute is present (added by opz telemetry)

Standard workflow

1. Generate traces on each target commit:

just e2e-trace

2. Collect per-ref report:

just trace-report <ref-or-version>

3. Compare two refs:

just trace-compare <base-ref-or-version> <head-ref-or-version>

4. For stable numbers, use multi-sample aggregation:

just trace-report-samples <ref-or-version> samples=5 status=ok
just trace-compare-samples <base-ref-or-version> <head-ref-or-version> samples=5 status=ok

Output

trace-report and trace-compare print markdown tables that can be pasted into PR comments and release notes.

Troubleshooting

• If no traces are found: increase fetch limit with limit=1000.
• If ref not matched: pass a longer commit prefix or explicit tag.
• If service differs: pass service=<name>.
• If failures skew results: set status=ok.

Reference

• Jaeger API details: references/jaeger-api.md