Revert #31: revived glitch alerts opened tickets

-25

1 Commits

Author	SHA1	Message	Date
jaredandClaude Opus 5.5	8edaa78ad7	Revert #31 : open link-down alerts from a monitor glitch were revived and ticketed Lint / JS (eslint) (push) Successful in 12s Details Lint / Python (flake8) (push) Successful in 1m47s Details Lint / Notify on failure (push) Skipped Details Lint / Deploy (push) Skipped Details Security / Python Security (bandit) (push) Successful in 1m15s Details Lint / JS (eslint) (pull_request) Successful in 7s Details Lint / Python (flake8) (pull_request) Successful in 48s Details Lint / Notify on failure (pull_request) Skipped Details Lint / Deploy (pull_request) Skipped Details Test / Python Tests (pytest) (push) Successful in 1m41s Details Security / Python Security (bandit) (pull_request) Successful in 1m32s Details Test / Python Tests (pytest) (pull_request) Successful in 1m6s Details #31 treated any open interface_down alert as previously up. Production had six such alerts all created in the same second on 2026-03-02 (a monitor glitch, on ports that were never in use: large1 enp36s0 and a USB adapter, compute-storage-01 nic1-3, micro1 enp3s0). Reviving them opened per-host tickets and a P1 cluster-wide ticket. Back to the previous behaviour while a safer fix is worked out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 01:11:00 -05:00

Revert #31: revived glitch alerts opened tickets #33