Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 14 days▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 14:14:51.
› →|
updated 1d ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.
← findings

chat-agent: p99 latency (ms) 1.5 min — 23.7× the fleet's usual 3.87 s (also p95 latency (ms) 8.25 s)

info Service outlier master open impact 13 Owner: Sambasiva Bandarupalli (backup: Ahmed Aburaed) opened 26d ago · last observed 1d ago · observed 932× · #5396 · 001e9ff2f6badc602d19

What happened template

chat-agent differs from the other 12 services on 2 measures over six hours: p99 latency (ms) 1.5 min against the peers' 3.87 s (29.4 MADs above); p95 latency (ms) 8.25 s against the peers' 1.28 s (6.7 MADs above). Peer comparison is structural more often than it is news — a service that does more work per request will sit here for as long as it does — which is why this is informational unless it is about failures.

A service unlike the rest of the fleet on one measure (robust z against its peers).

The facts

measures{'measure': 'p99 latency (ms)', 'value': 91800.00000000007, 'value_fmt': '1.5 min', 'median': 3873.749999999991, 'median_fmt': '3.87 s', 'mad': 2993.27492058822, 'z': 29.37459883662185, 'direction': 'above', 'peers': 12}, {'measure': 'p95 latency (ms)', 'value': 8249.999999999993, 'value_fmt': '8.25 s', 'median': 1275.9683098591524, 'median_fmt': '1.28 s', 'mad': 1048.0800217391302, 'z': 6.654102306585799, 'direction': 'above', 'peers': 12}
measurep99 latency (ms)
value91,800
value_fmt1.5 min
median3,874
median_fmt3.87 s
z29.37
directionabove
peers12
rule{"min_score": 3.5, "min_relative_pct": 35, "warn_on": []}
discriminator
window2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC

What is failing in chat-agent — the bad events, decomposed

“Bad events” are HTTP 5xx answers from chat-agent. In this finding's window (2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

44× Exception in ASGI application since 2026-09-03 07:34:47 UTC
2× Unhandled TimeoutError on POST /api/v1/chat/0abd2ffa-9e13-461c-8d2f-b08bed72f6b4/runs/stream since 2026-11-04 12:11:50 UTC

All chat-agent errors, grouped → · service page · its logs

History

Check it yourself

Every link carries the finding's own time window, so it shows tomorrow what it shows now.

Actions

Sign in (IAP) to acknowledge, snooze or resolve.

Where the numbers come from

sourcerollup
collected_at1794911364
age_seconds678
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteNone
detectoroutliers