logwatch de-noise refinement: chronic ≥2-day escalation + narration-line precision #340
Labels
No labels
Agent
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Total time spent: 10 minutes 31 seconds
Due date
igor
10 minutes 31 seconds
No due date set.
Dependencies
No dependencies set
Reference
joshtronic/igor#340
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refinement on top of the logwatch backoff-suppression MVP (#334). Held until #334 merges.
Scope
auth/limitbackoffs fire on ≥2 DISTINCT days, DO file a logwatch ticket (chronic ≠ noise; the once-daily health email may under-surface a recurring problem). Track distinct backoff days in state.health: auth alert emailed,backoff active (kind=...), logwatch's ownreview call failed/no parseable review), so a genuine unrelated failure in the same window still files.Constraints
bin/tick.shdo_logwatch_tick; new logic + tests only; 50-turn budget, build-verify-stop. Depends on #334 (MVP) on master.