5 Commits

Include renames

Author	SHA1	Message	Date
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	c625528191	fix(mcp): a failing router in get_overview says since when, as the page does (#5860) ... router_findings never passed `since`, so every failing router read as brand new and sorted last among the criticals. The overview now reads the failing routers' last day of history and dates each one with problem_since, as the dashboard widget does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 15:40:35 -04:00
bvandeusenandClaude Opus 5.5	80674603bc	fix(traefik): a router's 5xx share is judged only over enough requests, like its 4xx share (#5859) ... Two 500s of about sixteen requests graded roundtable@swarm critical at 9.1%. The Settings → Thresholds minimum of requests in 15 minutes (30 by default) now guards both shares; the 5xx share still keeps its fixed cutoff whatever the router's history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 15:35:57 -04:00
bvandeusenandClaude Opus 5.5	684a47b3eb	feat(mcp): Traefik routers, certificates and traffic (#5838) ... list_routers grades every router as the Traefik page does (the last 15 minutes, 5xx on its cutoff, 4xx and p95 against the router's normal) and gives a troubled one its status codes, what they mean and the swarm service behind it. get_router adds its history, codes, normal and anomalies; list_certificates the served certificates and the routers they cover; get_traffic the access log's clients, countries and routers. get_overview names a router answering 5xx and a certificate near expiry. The access-log aggregation moves into routes.summarize_access, shared by the traffic page and get_traffic. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 13:26:34 -04:00