4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 4.8	8f1c8c5cf7	feat(docker): container log viewer + Settings controls [M79 step 5] ... The user-facing half (rule 27). Per-container log viewer + admin controls, so container logs are something the operator can actually touch. Viewer (plugins/docker): - /container/<host>/<name>/logs full page + /logs/lines HTMX fragment polled every 5s (near-live follow); stream filter (all/stdout/stderr) + case-insensitive text search; newest-first so the latest lines survive the poll's scroll reset; empty/loading states; a "View logs" link from the container detail page. Jinja auto-escapes log content (no markup injection). Settings (Thresholds & Retention tab): - global on/off toggle, comma-separated exclude list, retention days + max MB per container — DB-backed, no restart. The toggle + exclude are enforced authoritatively at ingest (_persist_logs drops disabled/excluded lines), since the push model has no channel to tell an agent to stop. Tests: route-defined smoke; template-parse covers the new templates; integration test for the ingest-time toggle + exclude enforcement. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CAGR73DUowdVFVvYzLXC5C	2026-07-19 18:58:20 -04:00
bvandeusenandClaude Opus 4.8	8af297670e	feat(metrics): roll plugin_metrics up to hourly to bound storage ... plugin_metrics grows by (sources × resources × ~30s cadence); keeping 90d of raw is a large table. Add a raw→hourly rollup (mirroring the Docker plugin) so only a short raw window is kept at full resolution, with hourly averages archived longer. - PluginMetricHourly model + core migration 0024 (plugin_metrics_hourly: avg/max/ count per source/resource/metric/hour, unique bucket constraint + lookup index). - steward/core/metrics_retention.rollup_plugin_metrics: date_trunc('hour') agg of raw older than the hour-aligned raw window, idempotent pg upsert into hourly, delete the rolled raw, prune hourly beyond the rollup window. - cleanup.py: plugin_metrics is no longer blanket-deleted at data.retention_days; _run_metrics_retention drives the rollup with windows read live from settings. - Settings: metrics.retention.raw_days (7) + rollup_days (90), tunable on the Thresholds & Retention page (new "Host metrics retention" card). - Chart read: _history_for_host merges the hourly rollup (older part of the range) with raw date_bin (recent part, capped ≤1h), so 30d charts keep working — recent at full resolution, older at hourly. Route passes raw_days from settings. - Tests: unit (cutoff helpers) + integration (rollup aggregates/prunes; history merges hourly + raw) against Postgres. Speed was already handled by the indexes + SQL aggregation; this is the storage lever (raw window ~10x smaller). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Jg27rgypiW2efULXJDtMC	2026-06-20 21:08:30 -04:00
bvandeusenandClaude Opus 4.8	faecac3ec6	feat(docker): retention + hourly rollup for metrics/events with Settings windows ... Bounds Docker time-series growth (the main scaling concern). New docker_metrics_hourly table + docker_006 migration; a plugin retention module (docker.run_retention capability) rolls raw docker_metrics older than the raw window into hourly averages (idempotent upsert), deletes the rolled raw rows, then prunes stale rollups + lifecycle events. Core cleanup.py drives it each hourly run via the capability (no plugin-model import), reading the three retention windows fresh from settings so changes apply without restart (rule 25). Settings → "Thresholds & Retention" gains a Docker retention card (raw / rolled-up / events windows, working defaults 7/90/30 days). Unit tests cover the hour-aligned cutoff/bucketing helpers; integration test exercises the real rollup-average + prune across both windows. Milestone 77 task #941. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Jg27rgypiW2efULXJDtMC	2026-06-18 21:40:57 -04:00
bvandeusenandClaude Opus 4.8	591706bd39	feat(settings): configurable monitoring thresholds ... Move the hardcoded warn/crit cutoffs into Settings -> Thresholds (DB-backed, live, no restart). New thresholds.* keys + to_thresholds_cfg() + a threshold_style(value, kind) jinja global that reads them; latency reuses the existing ping good/warn keys, uptime is direction-aware (floors). Replace the _macros metric_style/uptime_style macros (now removed) with the global across Hosts-Overview, host_agent fleet + panel, Uptime/SLA widget, and the ping page uptime column — all now honor the configured cutoffs. Uptime keeps its green 'good' look when not degraded. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-17 20:52:58 -04:00