getsentry
Escalating issues algorithm doesn't take into account inactive previous week
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Have an archived issue that received no errors during the previous week, but then started receiving tens of errors during the current week.
Expected Result
The issue should be marked as escalating since 0 -> 15 errors in one hour is a sudden difference.
Actual Result
The issue is not marked as escalating because there is no data from the previous week to set an escalation limit with.
Issue link in the shadow ticket.
Product Area
Issues
Link
No response
DSN
No response
Version
No response
┆Issue is synchronized with this Jira Improvement by Unito
![getsantry[bot] avatar](https://avatars.githubusercontent.com/in/66573?v=4 "Published by a pub.dev verified publisher"){kind=small}
Going to look into this one to see if the algorithm did something abnormal, but it may just be that the volume didn't exceed the necessary threshold to be marked as escalating.
If an issue has not been seen in 7 days and the previous threshold expired, a threshold of 10 is set for the issue when it is triggered again (see here).
In this case, I'm guessing that the small spike on August 20th set the threshold to above 20 and that is why this issue didn't escalate.
I will close this for now since the escalation algorithm does take inactive previous weeks into account, but please re-open this if an issue that has been inactive for 2 weeks does not escalate with a count over 10.
