Findings 0
What X-ray is prepared to defend about automation 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.
Nothing to defend in this time range.
No finding matches these filters in this time range. That is the good state — but check the Detectors page: a detector that has not run is silent in exactly the same way as a fleet that is fine.