Baselines
X-ray's memory of what normal looks like on master. 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.
Normal for this hour is about 14.7 req/min (typically 0.0 req/min to 46.7 req/min) — within normal.
58 hours compared with their normal; 9 could not be — X-ray has not learnt those hours yet.
- Tue 02:00 15.0 req/min, normal ≈ 0.1 req/min 150.0× normal see it →
- Tue 00:00 16.8 req/min, normal ≈ 0.4 req/min 42.1× normal see it →
- Mon 12:00 390 req/min, normal ≈ 17.1 req/min 22.8× normal see it →
- Mon 14:00 264 req/min, normal ≈ 13.4 req/min 19.7× normal see it →
- Mon 13:00 257 req/min, normal ≈ 13.0 req/min 19.8× normal see it →
- Mon 17:00 162 req/min, normal ≈ 15.3 req/min 10.6× normal see it →
- Mon 15:00 156 req/min, normal ≈ 18.2 req/min 8.6× normal see it →
- Mon 07:00 128 req/min, normal ≈ 16.9 req/min 7.6× normal see it →
- Mon 18:00 194 req/min, normal ≈ 37.3 req/min 5.2× normal see it →
- Mon 09:00 220 req/min, normal ≈ 36.8 req/min 6.0× normal see it →
Not learnt yet: 25 scattered hours. An hour counts once two different weeks stand behind it, so the rest fills in as weeks pass.
whole cluster · Traffic requests per minute
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.