4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	4ded8ecee4	fix(mcp): get_anomaly shows a quick Steward restart, not only a gap over 90 s (#5862) ... A redeploy's new process ticks at once, so its once-a-minute samples never broke for 90 s and get_anomaly showed none of the day's restarts. The first self-monitor tick in a process now records restart_gap_secs (time since the last process's last sample), and steward_gaps shows each one as a restart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 16:11:27 -04:00
bvandeusenandClaude Opus 5.5	622addc09e	fix(mcp): get_anomaly keeps the events nearest the occurrence and says how many it left out (#5861) ... Each source in an anomaly's `around` was cut to its oldest 40 with nothing in the reply to say so; on a busy host the events nearest the occurrence were the ones dropped. Each source now keeps the 40 nearest the occurrence's start, and `around_left_out` counts the rest. Sources return everything their bounded query read (Docker and the host agent no longer cut at 40 and 20 themselves), so the count is honest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 15:59:16 -04:00
bvandeusenandClaude Opus 5.5	91bb199d14	fix(mcp): get_anomaly shows Steward's own restarts beside every anomaly, and a router's containers (#5862) ... All 16 Traefik 4xx anomalies on 2026-10-15 came back with nothing around them, though 15 were Steward's own restarts. A router has no host, and every events source was read by host. - Core: each break of more than 90 s in Steward's once-a-minute health sample is a "steward" event beside every anomaly, placed or not. - Plugins: an optional mcp_resource_events(db, source, resource, since, until) for a resource with no host. Traefik's gives the container events of the swarm service behind a router, on any host. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 15:58:28 -04:00
bvandeusenandClaude Opus 5.5	0945d78290	feat(mcp): understand and judge a metric anomaly: what happened, what was usual, what else went on (#5837) ... get_anomaly gives each occurrence against what is usual at that hour, the metric around the newest one with its normal, what else happened on the resource's host around each occurrence (alert transitions, Ansible runs, other anomalies there and a count elsewhere, plus plugins' own events through a new mcp_events hook: the host agent's maintenance jobs and downtime, Docker's container starts, deaths and OOM kills), and how earlier anomalies on the same metric were judged. get_metric_normal reads the learned slots and the level that would be flagged. review_anomaly takes one id or several, all or nothing, with a note. get_anomaly_settings and (admin) set_anomaly_settings read and change the review window and each normal's floor, as Settings → Thresholds does. metric_series.points takes an optional `until`; core.alerts gains host_of_resource; floor_setting names its floor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 13:17:34 -04:00