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 0.2 req/min (typically 0.0 req/min to 0.8 req/min) — within normal.
72 hours compared with their normal; 28 could not be — X-ray has not learnt those hours yet.
- Mon 11:00 17.7 req/min, normal ≈ 0.2 req/min 88.6× normal see it →
- Mon 10:00 11.6 req/min, normal ≈ 0.2 req/min 57.8× normal see it →
- Tue 07:00 25.5 req/min, normal ≈ 0.7 req/min 36.4× normal see it →
- Tue 06:00 12.4 req/min, normal ≈ 0.4 req/min 31.0× normal see it →
- Mon 12:00 57.1 req/min, normal ≈ 0.0 req/min inf% above normal see it →
- Tue 09:00 21.8 req/min, normal ≈ 1.4 req/min 15.5× normal see it →
- Mon 14:00 36.7 req/min, normal ≈ 0.0 req/min inf% above normal see it →
- Mon 15:00 21.7 req/min, normal ≈ 0.0 req/min inf% above normal see it →
Not learnt yet: 47 scattered hours. An hour counts once two different weeks stand behind it, so the rest fills in as weeks pass.
studiosvc · 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.