Skip to content

fix: Whoopsy! band re-learns after a lasting shift (v0.13.2) - #31

Merged
yakari007 merged 1 commit into
masterfrom
fix/whoopsy-relearn
Oct 11, 2026
Merged

yakari007 merged 1 commit into
masterfrom
fix/whoopsy-relearn

Conversation

@yakari007

Copy link
Copy Markdown
Contributor

Problem

The Whoopsy! band is frozen while values break it. A lasting level shift therefore never became the new normal: mean and bounds stayed flat, hits grew without end and the incident never resolved (seen on the Homepage HTTP check: 60/60 results outside, mean fixed at 82.29, hits 82).

Fix

The state keeps the latest outliers. After 5 × max(window, consecutive) results in a row outside the band, they replace the window, hits resets and the incident resolves. Shorter incidents alert as before. No schema change; existing check_state rows work.

Tests

TestWhoopsyRelearn added; go test ./internal/engine ./internal/threshold pass.

🤖 Generated with Claude Code

The band froze while values broke it, so a level shift that stayed
never resolved: mean and bounds stayed flat and hits grew without end
until someone reset by hand. The engine now keeps the latest outliers
and, after WhoopsyRelearn (5) times the longer of window and
consecutive results outside the band, takes them as the new window.
The incident resolves and the band follows the new level.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@yakari007
yakari007 merged commit 5188db2 into master Oct 11, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant