CLI Request Tracing

"It was slow" is not a useful answer when an endpoint regresses. atra gives you a real one.

Add -t and you get a waterfall

atra https://api.example.com -t

The output drops a phase-by-phase breakdown directly under the response, with proportional bars so the eye lands on the bottleneck immediately:

• Prepare — request building overhead
• DNS Lookup — name resolution time
• TCP Handshake — connection establishment
• TLS Handshake — certificate exchange and key setup
• Request Send — bytes pushed onto the wire
• Server Response — time-to-first-byte from the upstream
• Download — body receive time
• Processing — client-side parsing

Details

• Works on every request type — single requests, redirects, flow steps
• Combine with -v (verbose) to see headers and body alongside the timing
• Bars are proportional to phase duration, so the bottleneck is visible at a glance
• Phase data is also available programmatically via JSON output (--json)