2 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	b889584906	test(anomalies): each test runs in one event loop (#5740) ... The app's pooled connections belong to the loop that opened them, so a second asyncio.run in one test failed with "attached to a different loop" (run 9116). Tests that do several passes now await them in one coroutine. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 13:46:51 -04:00
bvandeusenandClaude Opus 5.5	5569f9934e	feat(anomalies): a metric out of its normal is an anomaly to review (#5740) ... #5740 "A metric that departs from its normal is recorded as an anomaly to review, and is findable after it ends", milestone 513. - Every minute each learned key's last 15 minutes is judged against its hour's normal: above the usual hold x1.25 and by the metric's floor opens an occurrence, which ends when the level comes back. - metric_anomalies holds one row per item to review; a repeat while it still waits joins it as an occurrence (metric_anomaly_spans). - An ended row nobody reviews within anomalies.review_days (14, Settings -> Thresholds) lapses; an ongoing one never does. - Learning skips every hour an occurrence covers unless its anomaly was marked normal: no normal is learned without review. - Alerts -> Anomalies lists those to review first, then the reviewed and lapsed under day dividers; marking is operator/admin and audited. - The Overview widget and get_overview warn of open ones and count those to review; the host page shows its own; the weekly report lists the week's and the lapsed; MCP list_anomalies and review_anomaly. - Reviewed and lapsed rows are pruned at data.retention_days, and kept in backups like alert history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 13:41:57 -04:00