The three kernel signals that tell an overloaded machine from a busy
one (Scenario#27.01); each is null where its source is unavailable.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
SystemHealth.assess combines RAM and disk headroom, load per core,
pressure-stall time and swap into healthy/pressure/overloaded
(Scenario#27.02); CPU utilization alone never counts.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
MetricsHistory is a column-wise ring buffer persisted with the
aggregation state (Scenario#27.03): 1440 minute points, 2880 quarter
points with average and maximum, a restart continues both.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
GET /api/system/history?range=day|month (Scenario#27.04) and the
runningBuilds list on GET /api/system (Scenario#27.05).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A verdict line, one gauge card per resource with a sparkline and the
peak of the selected range, a tile strip, and a 24 h / 30 d toggle
(Scenario#27.05); the all-time min/max/avg table is gone from the page.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The first rollout rendered the new system page with the browser's
cached old stylesheet and script; no-cache, must-revalidate makes a
deploy visible at once at the cost of a 304 per load.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1 h, 4 h, 24 h, 7 d and 30 d; the charts are taller and carry a time
axis, so an hour of data on a day's axis is recognizable as such.
The PR-doc's Solution section, lost to a silent edit, is restored.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Many builds last less than a minute and fell between two samples. The
history gains a third tier (15 s samples for four hours; minutes and
quarters carry average and maximum), the state file is written once a
minute and on shutdown, and the page opens on the last hour.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
mi
marked the pull request as ready for review 2026-09-08 11:41:46 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
Pull request closed