diff --git a/docs/plugins/host-agent-design.md b/docs/plugins/host-agent-design.md index c30387f..01dcabf 100644 --- a/docs/plugins/host-agent-design.md +++ b/docs/plugins/host-agent-design.md @@ -271,6 +271,8 @@ A board's spare thermistor inputs (a Nuvoton's SYSTIN, AUXTIN*) are often wired The verdicts are kept in memory and rebuilt at startup, so ingest and the host page read them without a query. The host page lists the sensors left out under "Not counted", each with its reason. A host with no CPU reading, or too little history, falls back to the value rule alone. +`temp_c_max` can drive an alert rule (#5787), e.g. "Host running hot": all hosts, over 85 °C for 10 consecutive checks. So can each sensor's `temp_c`, and the per-interface and per-disk throughput. `tests/core/test_metric_catalog.py` holds every metric ingest writes to the alert catalog, except the few `NOT_ALERTABLE` names in `plugins/host_agent/__init__.py`. + ### Logging To stderr only (systemd captures to journal). No file logging, no log rotation. Levels: diff --git a/plugins/host_agent/__init__.py b/plugins/host_agent/__init__.py index b8a7ba5..3140582 100644 --- a/plugins/host_agent/__init__.py +++ b/plugins/host_agent/__init__.py @@ -78,7 +78,18 @@ def get_alert_metrics() -> dict[str, list[str]]: reboot_required is 1 when the host needs a reboot (agent ≥ 1.16.0): "security updates waiting" is updates_security > 0. maintenance_failed comes from the scheduler (#5768): 1 when the host's latest maintenance job - failed or timed out, 0 once one succeeds: "maintenance failed" is > 0.""" + failed or timed out, 0 once one succeeds: "maintenance failed" is > 0. + temp_c_max is the host's hottest real thermometer, in °C (#5787); sensors + with nothing wired to them are left out (#5759, #5783): "running hot" is + > 85. temp_c is one sensor, resource ":temp: