Monitor: keep checking interfaces whose link-down alert is still open

+25

1 Commits

Author	SHA1	Message	Date
jaredandClaude Opus 5.5	d07787ee38	Monitor: keep checking interfaces whose link-down alert is still open Lint / JS (eslint) (push) Successful in 8s Details Lint / Python (flake8) (push) Successful in 49s Details Lint / Notify on failure (push) Skipped Details Lint / Deploy (push) Skipped Details Security / Python Security (bandit) (push) Successful in 53s Details Test / Python Tests (pytest) (push) Successful in 1m3s Details Lint / Python (flake8) (pull_request) Successful in 55s Details Lint / JS (eslint) (pull_request) Successful in 6s Details Lint / Notify on failure (pull_request) Skipped Details Lint / Deploy (pull_request) Skipped Details Security / Python Security (bandit) (pull_request) Successful in 1m22s Details Test / Python Tests (pytest) (pull_request) Successful in 1m27s Details After the interface baseline is reset, a port that is already down reads as "first seen down", which neither alerts nor resolves. An alert opened before the reset was then stuck open without updates: micro1's enp3s0 had sat at one failed check since March with no ticket. An interface with an open interface_down alert is now treated as previously up, so the alert keeps counting, tickets and resolves as normal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 01:02:53 -05:00

Monitor: keep checking interfaces whose link-down alert is still open #31