Disk fill forecasts, skeleton loaders, and a Silence button on alerts
A disk that is on course to be full within 14 days (setting: 0 turns it off) is flagged on the Alerts page and dashboard, from the server's own history: needs three days of steady growth, skips erratic disks and ones the ordinary disk alert covers. Skeleton placeholders replace "Fetching status…" and "Loading…". Alerts that a maintenance window can silence get a Silence button (1, 4 or 24 hours) that starts one, and the alert list is refreshed at once when a window starts or ends. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
82974b98d0
commit
f7f5e1cd41
24 files changed
+566
-25
No files matched your search
@@ -310,6 +310,18 @@ tickets, and integrations whose calls keep failing. It runs the same checks that
|
||||
send the notifications — so the two can't disagree — but ignores the on/off
|
||||
toggles, since it's for looking at rather than being interrupted by. Problems
|
||||
under a maintenance window stay listed, marked silenced and counted separately.
|
||||
It also looks ahead: from an agent server's own history (see its Trends card), a
|
||||
disk that is on course to be full within 14 days (Settings → Notifications → "Warn
|
||||
when a disk will fill within"; 0 turns it off) is flagged with its rate of growth
|
||||
and the days left — critical when that is three days or less. It needs at least
|
||||
three days of steady growth to say anything, skips a disk that jumped once or
|
||||
wobbles, and leaves out one already past the usual disk threshold, which has its
|
||||
own alert. These forecasts appear on the page and the dashboard (and in alert
|
||||
tickets if you've chosen disk problems); they are not sent as notifications. On
|
||||
any alert that a maintenance window can silence, operators and admins get a
|
||||
**Silence** button (1, 4 or 24 hours): it starts a maintenance window on that
|
||||
server or integration — so everything about it goes quiet, which the toast says —
|
||||
and it can be ended early under Maintenance.
|
||||
It checks live (a recent result is reused for a minute; "Check now" forces a
|
||||
fresh one), and anything it couldn't read is called out at the top rather than
|
||||
quietly treated as fine.
|
||||
|
||||
Reference in new issue
Block a user