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

..

alerting.md

feat(alerts): a rule can fire when a reading rises, "rose by N" (#6724)

2026-10-30 19:03:29 -04:00

ansible.md

fix(ansible): overlapping runs: one per host, one per schedule, one action run per alert rule (#5158)

2026-10-06 21:24:51 -04:00

backups.md

feat(mcp): Steward's own backups: the runs, the next one, checking and making one (#5836)

2026-10-15 13:09:12 -04:00

configuration.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00

mcp.md

feat(hosts): the hottest sensor is named with its chip, and the host-reading cutoffs are read and set over MCP (#6806)

2026-11-03 17:39:31 -05:00

monitors.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00

tickets.md

feat(tickets): open, comment and resolve tickets from the UI and MCP; known issues on alerts and anomalies (#6351, #6352)

2026-10-24 22:06:43 -04:00

timeline.md

feat(tickets): open, comment and resolve tickets from the UI and MCP; known issues on alerts and anomalies (#6351, #6352)

2026-10-24 22:06:43 -04:00