Xray
hourly rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 48 hours▾
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 09:54:54.
› →|
updated 23h 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.

Baseline coverage

Which services X-ray has learnt normal for on automation, measure by measure. Each cell is how many of the week's 168 hours have a baseline; an hour needs at least two different weeks of five-minute data behind it before it counts. Click a cell to see that week.

12 services 39 of 65 service × measure pairs learnt from 2–6 weeks of history rebuilt 1d ago
152+ hours — a full week 84–151 — half a week or more fewer than 84 nothing learnt: too little traffic, or under two weeks of data
ServiceTrafficrequests per minuteErrors% of requests failing (4xx + 5xx)Server errors% of requests returning 5xx — what alerting treats as an errorLatencyp95 response timeNeo4jqueries per minute
advpsvc 40/16814/16813/16813/16845/168
app 71/168———69/168
chat-agent 88/1688/1688/1689/16885/168
dashql 59/16863/16867/16869/16859/168
dashrsvc 82/168———85/168
data_monitor 76/168———73/168
docproc 100/16852/16854/16852/168103/168
exportsvc —1/1681/1681/168—
notifsvc ———1/168—
regsvc —3/1683/1683/168—
tusker —1/1681/1681/168—
virtual-assistant —1/1681/1681/168—

Rebuild

The Baseline refresh system alert does this nightly; press it after a data fix or a backfill.