3 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	5a0e150789	refactor(docker): container CPU and memory live in the one metric store (#5752) ... #5752 "Container CPU and memory history lives in the one metric store; docker_metrics and docker_metrics_hourly are retired". Container cpu_pct and mem_pct already went to plugin_metrics for alerting; now mem_usage_bytes does too, and every snapshot in an ingest (backlog included) is recorded at its own time. The container history chart, Busiest Containers, a service's history and the MCP container tools read plugin_metrics under resource "<host>/<container>", rolled up and pruned by the shared metric retention. docker_012_drop_metrics drops both tables. Their history is not copied (lesson #5221 "A data migration's cost is set by the live table"); the store already holds 7 days of container CPU and memory %. Docker retention now prunes only lifecycle events, and Settings -> Thresholds has one "Metric retention" card for every source. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 14:39:56 -04:00
bvandeusenandClaude Opus 5.5	30f4de3612	fix(docker): drop the unused .w-meter style; the bars test reads the loaded plugin's models (#5214) ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 15:08:15 -04:00
bvandeusenandClaude Opus 5.5	05eaca3f2f	feat(docker): Busiest Containers shows bars of the last hours beside each figure, scaled to the row's peak with a floor (#5214) ... The fill bars were a share of the host's capacity, a sliver on hosts with 80 cores. Each figure now sits beside 24 bars of the last 6 hours (1h/24h per widget), each row scaled to its own peak but never below 1 core or 1 GiB (configurable per widget), so a 0.05-core container reads flat and a bar's height means real load. One grouped date_bin query feeds them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 15:05:06 -04:00