Files
pulse/internal
rcourtman 33bcf698e0 Keep node temperature alerts when a host agent runs on the node
Installing a Pulse agent on a Proxmox node silently ended CPU
temperature alerting for it. CheckNode skipped every node metric,
temperature included, once a host agent with the node's hostname
registered, but CheckHost evaluates only CPU, memory and disk usage and
SMART disk temperatures, never CPU temperature. On pulse-prod the last
node temperature alert fired on 5 October; delly2 has since read 90°C
and minipc 78-87°C with no alert.

Temperature now stays with the node whether or not an agent is
registered. The node poll already merges the agent's sensors into
node.Temperature, so this gives one temperature alert per machine.

The dedup skip path also never cleared node alerts it stopped
evaluating, so a node alert open when the agent registered stayed
frozen until the agent went offline. pulse-prod shows this today: the
delly2 node memory alert, open since 29 September, beside the agent's
own memory alert. CheckNode now releases node CPU, memory and disk
alerts through the disabled-threshold path, which drops the pending run
and resolves the open alert, leaving the agent as the only owner.

A missing CPU reading also fed 0°C into the evaluator, which could
resolve an open temperature alert without any evidence that the node had
cooled. With a live trigger the check now skips the evaluation instead,
while a disabled threshold still clears.
2026-10-06 13:43:47 +01:00
..