Source: Full code review 2026-07-17 (docs/reviews/2026-07-17-full-code-review.md), finding F10.
Category: docs/code mismatch · Severity: low · Effort: small
Problem
packaging/pimonitor.example.yaml:60-61 says the thresholds section drives "the load-average gauge scale, which uses the CPU thresholds relative to core count", but renderGauge (internal/web/assets/app.js:486-491) uses fixed cores × 0.7 / cores × 1.0.
Suggested fix
Either use cpu_warn_percent / cpu_crit_percent relative to core count as documented (cores × cpu_warn_percent/100), or correct the comment in the example config.
Source: Full code review 2026-07-17 (
docs/reviews/2026-07-17-full-code-review.md), finding F10.Category: docs/code mismatch · Severity: low · Effort: small
Problem
packaging/pimonitor.example.yaml:60-61says the thresholds section drives "the load-average gauge scale, which uses the CPU thresholds relative to core count", butrenderGauge(internal/web/assets/app.js:486-491) uses fixedcores × 0.7/cores × 1.0.Suggested fix
Either use
cpu_warn_percent/cpu_crit_percentrelative to core count as documented (cores × cpu_warn_percent/100), or correct the comment in the example config.