diff --git a/status/index.html b/status/index.html index f6c23df..6b09ffc 100644 --- a/status/index.html +++ b/status/index.html @@ -694,9 +694,9 @@ ⚠️
Disk Usage Note: - DashCaddy stores health check history, container statistics, and event logs. - On a busy server, this data can accumulate over time. - Set appropriate retention limits in Settings → Health to prevent disk fill. + DashCaddy stores up to 500 health check entries per service (plus container statistics and event logs). + At high check frequencies this may consume significant disk space — on a host with many services the history file can grow to tens of megabytes. + Adjust the health check interval, max entries per service, and health retention period in Disk Safety (the 💾 Disk button in the top bar) to control disk usage.
@@ -704,12 +704,12 @@
📋 Recommended after setup
diff --git a/status/js/disk-settings.js b/status/js/disk-settings.js index dc77ced..65ae14c 100644 --- a/status/js/disk-settings.js +++ b/status/js/disk-settings.js @@ -47,6 +47,15 @@ +
+
+ ⚠ Disk impact: Lowering the health check interval increases how often data is written to disk. + DashCaddy caps history at max entries per service and prunes entries older than the retention period, + so these two values together determine steady-state disk usage. For busy hosts, prefer a longer interval (60–120s) + and a lower entry cap. +
+
+
${settingRow('Health Check Interval', 'healthInterval', c.healthCheckInterval, 'seconds', Math.round((c.healthCheckInterval||30000)/1000), 5, 300)} ${settingRow('Max Health Entries/Service', 'healthMaxEntries', c.healthMaxEntries, 'entries', c.healthMaxEntries||500, 50, 5000)}