CRITICAL: TLS expiry warning fires on every check cycle with no deduplication #18
Atsaukties uz šo jaunā problēmā
Block a user
Dzēst atzaru "%!s()"
Atzara dzēšana ir neatgriezeniska. Kaut arī izdzēstais zars neilgu laiku var turpināt pastāvēt, pirms tas tiešām tiek noņemts, to vairumā gadījumu NEVAR atsaukt. Vai turpināt?
Bug
checkTLSExpiry()ininternal/watcher/watcher.gosends a notification every time a TLS check runs if the certificate is within the warning window:There is no state tracking whether a warning has already been sent for this certificate. With the default 12h TLS interval, this means 2 warnings per day, every day, until the cert is renewed.
Impact
Notification spam to Slack/Mattermost/ntfy. Users will mute the channel, defeating the purpose of monitoring.
Fix
Track last-warned state (e.g., in
CertificateState) and only re-send if the expiry crosses a new threshold (e.g., 7 days, 3 days, 1 day, expired) or if the certificate changed.