Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 5 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:36:49.
› →|
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 3

stored age unknown all 3detectors over stored rollups and live sources

What X-ray is prepared to defend about test27 right now — each one a claim with its numbers, the evidence to check it, and what normal looks like. Detectors last ran never. ?A finding is opened by a detector — a statistical test over the stored rollups, or a live check of a source — and stays ONE row while the condition persists: it updates, escalates, and resolves itself fifteen minutes after the detector stops seeing it. Acknowledge to say you have it; snooze to hide it for a while; nothing here is a threshold somebody configured.

How to read this page — how findings work

Every card is a claim X-ray can back with numbers you can click through to. Findings rank by severity first, then by an impact score (severity band + the subject's share of the cluster's traffic + how long it has been open), so the top of the page is the thing to look at first.

anomaly
Three of the last four five-minute buckets far outside what this hour of THIS weekday normally sees — median ± MAD over the last 2–8 weeks, not a threshold.
outlier
A service unlike the rest of the fleet on one measure, over six hours. Compares with peers, not with its own history — the two catch different things.
budget
Burn rate against an error objective derived from the service's own last week, and the date the 30-day budget runs out if the trend holds.
resolves itself
A finding a healthy detector run no longer observes resolves after fifteen minutes. A detector whose SOURCE fails resolves nothing — it says so on the Detectors page instead.

What this page will not tell you

  • That a finding is a diagnosis. It is a measured departure from normal with adjacent changes listed; the narrative says 'adjacency, not proof' and means it.
  • Anything about hours the ingester did not cover. A bucket with no rows is a gap, not a quiet period, and the baselines skip it.
  • Anything on the first day for the novel-error detector: its 90-day memory learns silently for 24 hours before it will call anything new.
show active resolved all severity everything warning + critical only clusters
test27
just test27 · nothing ticked means test27, the cluster selected up top
or just close the list
group all AnomaliesReliabilityNeo4jChangesJourneyX-rayWeaviateAIPodsJobsPlatformErrorsCustomCostCapacity + 4 fleet-wide 0 critical · 11 warning · 14 info detectors
warning Pod keeps restarting test27 resolved last seen 1d ago · since 1d ago · 1×

jss-server on test27 has restarted 9 times in 10 min — crash loop, image spreadsheet-agent-edits-d3202c0

jss-server in tilda on test27 has restarted in place 9 times since 2026-11-17 10:05 UTC (9 in the last 30 minutes, 9 in 24 hours), most recently at 2026-11-17 10:15 UTC. Kubernetes' account of it: 11 crash events, 3 sched events. Last event: BackOff — “Back-off restarting failed container jss-server in pod jss-server-5968bc86d8-pptmg_tilda(fda1a1d7-5f21-42bd-b73d-7d92a2cf2383)”. It is running image spreadsheet-agent-edits-d3202c0. Containers restarting: jss-server ×9. The workload carried 0.0% of the cluster's API calls in the last day. Restarts are counted from the container restart counter, so a rollout or a spot preemption does not count; a crash does. It resolves on its own after thirty quiet minutes.

warning Service gone silent test27 Owner: Prasad Limaye (backup: Sambasiva Bandarupalli) resolved last seen 1d ago · since 69d ago · 93×

onboardingsvc on test27 has served nothing for 40 min; at this hour it normally serves about 132 calls/hour

onboardingsvc on test27 has served no API calls for 40 minutes (last call 2026-11-17 05:00 UTC); at this hour of the week its baseline — 5 weeks of history — expects about 132 calls an hour, 66 in the window checked. It carried 10.6% of the cluster's calls over the last week. Silence is not measured downtime: the pods may be up and unused, or crashed, or cut off upstream — Reliability and Pods say which. It resolves on its own once the service serves again.

warning Error budget burning test27 Owner: Prasad Limaye (backup: Sambasiva Bandarupalli) resolved last seen 3d ago · since 26d ago · 210×

onboardingsvc is burning its error budget at 7.3× (1 h) / 7.4× (6 h) against a 99.00% objective

onboardingsvc is spending its error budget 7.3× faster than the objective allows over the last hour (7.4× over six hours). The objective is 99.0%, derived — a baseline, not a promise. 69 bad events against 929 calls in the window.