Repository navigation
Fix notification consistency and Syslog alert priorities for v1.6 - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope\n- Send structured, bounded alert records to Syslog with correct CRITICAL/HIGH/WARNING/INFO priorities; keep INFO recovery events.\n- Suppress routine INFO and WARNING polling chatter from remote Syslog while retaining operational errors and alerts. Per-container periodic logs become DEBUG.\n- Align SMTP and Slack alert content, including probe evidence, actions, runbooks, and HA severity.\n- Include confirmed OOM memory snapshot when available; retain exit-137 SIGKILL vs OOM distinction.\n- Keep five SNMP var-binds and OIDs unchanged for compatibility.\n\n## Validation\n- 104 Python unittest tests passed on m920q in isolated venv.\n- Real local UDP Syslog receiver: verified priorities 2, 3, 4, 6 (local0 messages PRI 130/131/132/134) and absence of routine INFO packets.\n- No changes to live watchdog or host configuration.\n\n## Release\nTarget release/v1.6.0; merge this fix before finalizing release PR #9.