The traffic charts stop counting us. The once-a-minute URL probes go through HAProxy on purpose — that is what makes them honest — so HAProxy counted them like anyone else's requests, and a service nobody visited showed a steady block of "traffic" that was only this app talking to itself. The probes now tally what they put through, per pool, and the history subtracts it at sampling time — including the 401 a sign-in answers a probe with, which was polluting the 4xx line. Zero visitors reads as zero. (HAProxy's backend health checks were never in these numbers.)
And stop exaggerating. A sparkline scaled purely to its own peak turned a flat 1 request a minute into a full-height wall that read as more traffic than a real rush on the row above it. The scale now never drops below 10 requests a minute, so a trickle draws as the low band it is; a window that recorded nothing says so in words instead of drawing a line; and server errors share the requests' scale, so three errors over three hundred requests are a hairline rather than a second mountain.
Verified against a live node: HAProxy's own counter for an untouched, probed service read 2 while the history stored zeros — and three real visits then landed as exactly three. History already recorded before this version ages out of the 24-hour window on its own.
Packages are attached below; the container image is at ghcr.io/avandeputte/haproxy-manager:1.85.2.