Follow the complete request.
Search, filter and expand the sample traces. Inspect the relationship between the route, provider wait, time-to-first-token and generation duration.
04 / TRACE EXPLORERFrom user request
From user request
to final token.
Search the sample request set, filter by execution context, and expand a trace to inspect its illustrative waterfall.
4 TRACES
| TRACE | TIME | ROUTE | MODEL | TTFT | TOTAL | TOKENS | COST | STATUS |
|---|---|---|---|---|---|---|---|---|
| 12:42:18.112 | support-prod | claude-sonnet | 284 ms | 820 ms | 1,842 | $0.014 | OK | |
| 12:42:17.891 | research | gpt | 431 ms | 1.18 s | 3,091 | $0.028 | OK | |
| 12:42:17.617 | chat | gemini-pro | 198 ms | 644 ms | 883 | $0.008 | OK | |
| 12:42:17.520 | copilot | llama | 712 ms | 2.02 s | 2,201 | $0.005 | FALLBACK |
EXPLORER GUIDE
Inspect the record, not just the total.
- Search the sample set
- Search by trace ID, model, route, provider, session or sample user label. Search remains inside the browser and does not query a production log store.
- Combine filters
- Filter by model, provider, latency band, status and example environment. Use Reset Filters to restore the complete sample set.
- Expand the waterfall
- Expand a trace to inspect SDK, gateway, policy, router, provider, TTFT and generation stages. Durations are illustrative and add up to that example trace’s total.
DATA CLASSIFICATION
Synthetic records, real interactions.
The controls work against four supplied example traces. They are not customer data or evidence that Orbitriva is processing production requests. For measured records you collect yourself, use the existing benchmark workspace.