Probabilistic systems / async evidence

See where the pipeline really spends time.

Load a span trace. Get the critical path, concurrency signal, failures, and a diagnosis you can carry into code review.

Trace input

Each span needs id,start_ms,end_ms. Optional: parent_id,name,kind,status.

Diagnosis

0spans observed
0 mswall-clock window
0 mssum of work
0%parallel overlap

Analysis appears here after a valid trace.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.