Home
support-agentTraces
3K
↑ 3.6%vs previous 7d
Error rate
7.3%
↑ 30%222 with errors
Latency p50
3.06 s
↓ 1.3%vs previous 7d
Latency p95
7.42 s
↑ 5.0%vs previous 7d
Total cost
$19.72
↑ 2.7%$0.00651 per trace
Tokens
8.6M
7.8M in · 848K out
A story in this data
Release v1.14.0 made refunds time out. v1.14.1 fixed it.
The refund agent's payment call started failing after the release and recovered a few days later. Follow the same path you would use on a real incident.
Traces over time, ok and with errors stacked · click a bar to zoomokwith errors
Most common errors
All error groups →- 62issue_refund · ToolTimeoutissue_refund timed out after <n>ms (request <id>). The upstream service did not respond.62 traces
- 47search_kb · ConnectionErrorsearch_kb could not reach the knowledge index (connection reset by peer, request <id>).47 traces
- 24lookup_order · ValidationErrororder_id 'ORD-<n>' was not found for customer cust_<id>.24 traces
- 20gpt-4.1-mini · RateLimitError<n> Too Many Requests: rate limit reached for gpt-<n>-mini on tokens per minute. Retry after <n>s (request <id>).20 traces
- 18gpt-4.1 · RateLimitError<n> Too Many Requests: rate limit reached for gpt-<n> on tokens per minute. Retry after <n>s (request <id>).18 traces
Releases
Latest failed traces
Open in Tracing →- order-statusToolTimeoutget_customer timed out after 3000ms (request e7f039a3). The upstream service did not respond.v1.14.1 · 4.57 s
- order-statusValidationErrororder_id 'ORD-51016' was not found for customer cust_9ez2n.v1.14.1 · 1.89 s
- refund-agentToolTimeoutsend_email timed out after 6000ms (request b7051308). The upstream service did not respond.v1.14.1 · 10.2 s
- refund-agentRateLimitError429 Too Many Requests: rate limit reached for claude-sonnet-4-5 on tokens per minute. Retry after 8s (request 65491ac0).v1.14.1 · 9.38 s
- refund-agentValidationErrororder_id 'ORD-78000' was not found for customer cust_36x1q.v1.14.1 · 1.78 s
- order-statusValidationErrororder_id 'ORD-87269' was not found for customer cust_35w0.v1.14.1 · 1.73 s