Anomaly detection: from unusual behavior to a useful signal
Baselines, event-level precision and recall, and the cost of waiting determine whether an unusual pattern belongs in investigation or paging.
Guides, news and explanations about AI and reliable systems.
Baselines, event-level precision and recall, and the cost of waiting determine whether an unusual pattern belongs in investigation or paging.
Observation, collection and evaluation timestamps explain why the last zero-error result may no longer describe the service.
A queued upload illustrates the choice of SLI, target and window, including why endpoint success can miss the user’s unfinished task.
Concurrent spans, retries and selected samples explain what a trace reveals about one request and where an investigation needs another observation.
Alert cleanup can reduce interruption or conceal a recurring failure. Customer reports and correction effort help distinguish the two results.
Worked request and time examples explain error-budget units, remaining allowance and burn rate, plus the release policy that gives them a practical role.
Worked formulas and a scorecard connect customer outcomes, response delays and specialist workload to reliability investment.