fix(ci): use 7-day rolling average for analytics anomaly detection#258
Merged
Conversation
The previous day-over-day comparison triggered false positives when traffic returned to baseline after a spike (e.g. 573→318 = -45%, but 318 is normal). Now compares against the 7-day rolling average with a -40% threshold, which is more resilient to natural traffic fluctuations. Closes #256 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
Problem
The old logic compared consecutive days, so a traffic spike ending (573→318) triggered a -45% alert even though 318 sessions is within the normal baseline (~377). This caused false positive #256.
Verification
Against March 4 data: 318 sessions vs 454 avg = -29.9% → would NOT trigger (correct)
Closes #256
Test plan
🤖 Generated with Claude Code