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 08:01:16.
› →|
updated 21h 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 10

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

What X-ray is prepared to defend about test26 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
test26
just test26 · nothing ticked means test26, the cluster selected up top
or just close the list
group all AnomaliesReliabilityNeo4jChangesJourneyX-rayWeaviateAIPodsJobsPlatformErrorsCustomCostCapacity + 4 fleet-wide 0 critical · 10 warning · 8 info detectors
warning 4xx spike (403/401/404…) test26 Owner: Suresh Boddapati (backup: Madhava Mukkamala) last seen 21h ago · since 7d ago · 164×

studiosvc GET /api/studio/events: 4xx — 100 of 100 calls (100 %; other 4xx×100) in the last 15 min — it rejects nearly every call

4xx spike (403/401/404…): studiosvc GET /api/studio/events: 4xx — 100 of 100 calls (100 %; other 4xx×100) in the last 15 min — it rejects nearly every call. Facts: endpoint GET /api/studio/events, service studiosvc, calls 100, c4xx 100, share_pct 100.0, c401 0.

info Service outlier test26 Owner: Suresh Boddapati (backup: Sambasiva Bandarupalli) last seen 21h ago · since 74d ago · 372×

enrollsvc: Neo4j queries per request 50.0 — 6.9× the fleet's usual 7.3

enrollsvc's Neo4j queries per request is 50.0 against the 5 other services' median of 7.3 (8.6 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.

warning Query shape degrading test26 resolved last seen 22h ago · since 20d ago · 14×

feedsvc shape 00000000: p95 4.85 s now vs 28 ms earlier (172.7×, 3,394 runs)

A feedsvc query shape on test26 has p95 4.8 s in the second half of the window against 28 ms in the first (172.7×, 3,394 executions). The shape reads: “RETURN EXISTS { MATCH (cfg2:WorkplanCfg) WHERE cfg2.progressPending = true AND coalesce(cfg2.lastViewedAtMs, ?) > (times…”. Slower can mean more data, a lost index, or lock contention — the shape page has the CPU/wait split. Shapes whose p95 stays under a second are never reported: below that nobody notices, whatever the ratio.

info Service outlier test26 Owner: Suresh Boddapati (backup: Sambasiva Bandarupalli) last seen 22h ago · since 74d ago · 91×

patientsvc: p99 latency (ms) 1.75 s — 3.3× the fleet's usual 530 ms

patientsvc's p99 latency (ms) is 1.75 s against the 5 other services' median of 530 ms (5.5 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.

info Service outlier test26 Owner: Madhava Mukkamala (backup: Shashank Agrawal) last seen 22h ago · since 83d ago · 617×

execsvc: p99 latency (ms) 1.95 s — 3.7× the fleet's usual 530 ms (also p95 latency (ms) 1.48 s)

execsvc differs from the other 5 services on 2 measures over six hours: p99 latency (ms) 1.95 s against the peers' 530 ms (6.4 MADs above); p95 latency (ms) 1.48 s against the peers' 257 ms (5.0 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.