Cost anomalies
Days a project × service × cluster cell sat far outside its own normal — each decomposed into what moved, and lined up with what X-ray saw that day.
7 days
14 days
30 days
90 days
This month
Last month
12 months
last 30 complete days · complete through 2026-11-17
How to read this page — Cost anomalies
Each cell's daily net is compared with the median of its own previous 28 days; the distance is measured in MADs (robust standard deviations), so one earlier spike does not hide the next. Open an anomaly for the decomposition by SKU, namespace and workload, and the day's API calls, Neo4j queries, deploys and findings for the same cluster.
- z
- robust z-score: (day − median) ÷ (1.4826 × MAD). 3.5 is the default threshold.
- Normal
- the median of the previous 28 days for that cell.
- Adjacent
- X-ray's signals for the same day are shown beside the cost; adjacency is not causation — rule 5 of Ask X-ray applies here too.
What this page will not tell you
- A spike inside a single day's hours — cost is daily below 21 days ago; the hourly profile is shown where the hourly table still has it.
- Anomalies in a period the ledger does not cover yet.
reading the cost ledger…