4 Commits

Include renames

Author	SHA1	Message	Date
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	35f658b573	feat(monitors): unify ping/dns/http into one Monitor entity + custom targets ... Collapse the three former check types into a single core `Monitor` entity with one management surface (/monitors), one result table (monitor_results), and a single scheduled task. Every type can now watch a free-standing custom destination (optional host_id) — not just a registered Host. - models: Monitor + MonitorResult replace PingResult/DnsResult; Host loses its ping/dns facet columns (now Monitor rows linked by host_id). - checks: monitors/{ping,dns,http}.py pure probes + runner.run_monitor dispatcher; one monitor_check scheduler with a per-monitor due-filter. - status: single monitor_status_source replaces the three sources. - UI: /monitors blueprint (type-aware add/edit/list/widget); host hub shows a host's linked monitors + "add monitor for this host"; nav + widget registry + alert metric catalog rewired. http plugin folded into core and removed. - migration 0022 merges the http branch, data-migrates host facets + http_monitors + all three result histories, drops the old tables/columns. Resolves the per-host ping/dns auto-attach issue (#275): monitors are now explicit, never auto-added to every host. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Jg27rgypiW2efULXJDtMC	2026-06-18 08:56:13 -04:00
bvandeusenandClaude Opus 4.7	88ab5b917e	chore: rename project Roundtable → Steward ... Renames the Python package directory, CLI command, env var prefix, docker-compose service/container/image, Postgres role/db, and all visible branding. Marketing form is "Fabled Steward". Clean break from the previous rebrand: drops the fabledscryer→roundtable import shim in __init__.py and the FABLEDSCRYER_* env var fallback in config.py and migrations/env.py. Env vars are now STEWARD_* only. Heads-up for existing deployments: - Postgres user/db renamed fabledscryer → steward in docker-compose.yml. Existing volumes need the role/db renamed inside Postgres, or override POSTGRES_USER/POSTGRES_DB to keep the old names. - Host-agent systemd unit is now steward-agent.service. Existing agents keep running under the old name; reinstall to switch. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-25 16:20:14 -04:00