4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	38ae99fb8e	feat(hosts): the hottest sensor is named with its chip, and the host-reading cutoffs are read and set over MCP (#6806) ... Agent 1.27.0 sends each temperature sensor's hwmon chip. Steward keeps the chip per host and label beside the reading, so a sensor's metric key stays its label, and the strip and the heat alert name it as "NVMe · Sensor 2" rather than a bare "Sensor 2". get_thresholds (viewer) and set_thresholds (admin, audited) read and change the warn/crit cutoffs CPU, memory, disk, load and temperature are graded by, as Settings → Thresholds does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-03 17:39:31 -05:00
bvandeusenandClaude Opus 5.5	ec13f3797d	perf(host_agent): the sensor judgment reads the week once, then only new hours (#5786) ... On the live instance the hourly refresh took 3 min 8 s, averaging a week of raw temp_c samples each time. The hourly averages are now kept in memory. The first refresh after startup reads the whole window. Each later one reads raw samples from the start of the hour the last read ended in, so the hour that was still filling is read again whole. merge_hours folds the new rows in and drops hours older than the window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 21:42:11 -04:00
bvandeusenandClaude Opus 5.5	2ade4ebc46	fix(host_agent): sensors are judged from the raw week, not only its rollups (#5783) ... Rollups exist only for hours older than the raw window (7 days by default), so the first deploy read an empty week and judged nothing. refresh now averages the raw samples by the hour and adds any rolled-up hours in the window. Sensors are named from plugin_metric_latest, so each series is read through its index instead of a pattern over every host_agent row. An integration test covers both halves against Postgres. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 21:33:36 -04:00
bvandeusenandClaude Opus 5.5	0b29cdf26c	feat(host_agent): a temperature sensor is judged by how it moves against the CPU (#5783) ... A board's spare thermistor inputs report whatever an open input reads, and the value rule from #5759 only catches the impossible ones. Once an hour, sensors.refresh judges each sensor against the host's CPU (Package id N, Tctl/Tdie/TccdN, PECI Agent N) over a week of hourly averages. A sensor is ruled out if it falls as the CPU warms (r <= -0.5) or holds within 0.5 °C while the CPU moved 10 °C or more. A judgment needs at least 72 shared hours. The host temperature leaves judged sensors out at ingest. The host page lists them under "Not counted", with each reason given once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 21:24:34 -04:00