2479560fa2
Some checks failed
ci/woodpecker/push/default Pipeline failed
MAMFarmingStuck fired whenever the freeleech grabber added 0 torrents in 4h, but grabbing 0 is normal: the grabber searches a random catalogue offset each run and legitimately finds nothing when freeleech is dry (account ratio was a healthy 37.5; the alert even misreported it as "0.00" because $value was the grabbed count, not the ratio). The alert's real intent was to catch the grabber not running at all (CronJob Forbid-blocked / wedged), but increase(grabbed[4h])==0 cannot distinguish "didn't run" from "ran, nothing to grab" since Pushgateway serves the last pushed value forever. The grabber now heartbeats mam_grabber_last_run_timestamp on every completed run (main success, ratio/mouse skip, and qBittorrent-unreachable paths). The alert fires only when that heartbeat is >4h stale — the true stuck condition. Cookie expiry and qBittorrent-down keep their own dedicated alerts. Surfaced by /cluster-health as a false-firing alert. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| files | ||
| main.tf | ||