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 11:11:58.
› →|
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.
← alerts

New alert

Say it in plain English and press Design alert — X-ray proposes the rule, you review it and press create. Or fill in the form by hand. Nothing is saved until you create it.

Describe it

claude-sonnet-5-5 reads it with the full catalogue of what X-ray records — every table and column, and the read-only tools that reach journeys, traces, logs, evals and tests — and writes the query; it runs the query before proposing it, and you see the rule, its result right now and a backtest before anything is saved. Anything X-ray records is alertable; when it does not record what you ask, it says so. Grouping words work too: at most once every 15 minutes, remind me every 2 hours, no reminders, one message per service.

Or fill in the form by hand
route these findings levels (tick any to route on levels) clusters (none = every cluster) kinds (none = every kind) AnomaliesReliabilityNeo4jChangesJourneyX-rayWeaviateAIPodsJobsPlatformErrorsCustomCostCapacity
the condition
the query — one SELECT returning a numeric value (and optionally a text label for one target per row); bind :since :until :cluster :now
fire on error logs — the moment an error appears, in real time (not the 5-minute finding cycle) clusters (none = every cluster)
deliver
grouping — many findings, one message per observation window (research: 09 and 15)