Baselines
X-ray's memory of what normal looks like on test27. For every service it remembers what a
typical Tuesday 14:00 — or any other hour of the week — looks like: how much traffic, how many errors, how slow, how
much Neo4j load. The Anomalies system alert compares live
numbers with this memory and raises a finding when
something is far outside it.
X-ray has not learnt this hour yet.
0 hours compared with their normal; 18 could not be — X-ray has not learnt those hours yet; 3 known from too few samples to judge.
Not learnt yet: Sat–Sun, most of Mon, most of Tue, most of Wed, most of Thu and most of Fri. An hour counts once two different weeks stand behind it, so the rest fills in as weeks pass.
docproc · Latency p95 response time
Rows are days, columns are hours of the day, in UTC — baselines are learnt per UTC hour, so the grid cannot shift with your timezone; the cards above give the times in UTC as well. Hover a cell for its numbers. ?How a finding is decided: three of the last four complete five-minute readings must be far outside their hour's normal — at least 4 scaled MADs and 35% away from the median, and above a small absolute floor so a quiet service cannot alarm on noise. An hour needs 20 readings behind it before it may raise anything. The thresholds are editable on the Anomalies system alert.