Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(crons): Add mark_unknown clock tick task #79735

Conversation

evanpurkhiser
Copy link
Member

@evanpurkhiser evanpurkhiser commented Oct 24, 2024

This task will be used when the clock ticks with the
volume_anomaly_result set to abnormal. In this scenario we must mark
ALL in-progress check-ins as "unknown", since we cannot be sure that the
completing check-in was not sent during the lost data that caused the
volume drop of check-ins.

Part of GH-79328

@evanpurkhiser evanpurkhiser requested a review from a team as a code owner October 24, 2024 21:59
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 24, 2024
Copy link

codecov bot commented Oct 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #79735      +/-   ##
==========================================
+ Coverage   78.41%   78.46%   +0.04%     
==========================================
  Files        7147     7159      +12     
  Lines      315845   316764     +919     
  Branches    43498    43608     +110     
==========================================
+ Hits       247685   248537     +852     
- Misses      61825    61878      +53     
- Partials     6335     6349      +14     

This task will be used when the clock ticks with the
volume_anomaly_result set to `abnormal`. In this scenario we must mark
ALL in-progress check-ins as "unknown", since we cannot be sure that the
completing check-in was not sent during the lost data that caused the
volume drop of check-ins.
@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/feat-crons-add-mark-unknown-clock-tick-task branch from 1d49328 to bc93d79 Compare October 25, 2024 19:14
#
# NOTE: We should keep an eye on this as we have more and more usage of
# monitors the larger the number of checkins to check will exist.
CHECKINS_LIMIT = 10_000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: this is the same as in other tasks.

Co-authored-by: Josh Ferge <josh.ferge@sentry.io>
@evanpurkhiser evanpurkhiser enabled auto-merge (squash) November 6, 2024 22:05
@evanpurkhiser evanpurkhiser merged commit f033b12 into master Nov 6, 2024
50 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/feat-crons-add-mark-unknown-clock-tick-task branch November 6, 2024 22:37
evanpurkhiser added a commit that referenced this pull request Nov 6, 2024
This causes clock ticks with the "volume_anomaly_result" set as abnormal
to dispatch a mark_unknown task instead of a check_timeouts task.

This is needed since when we detect an anomalous tick we're unable to
know if we lost customer data during that tick, meaning all in-progress
check-ins that were waiting for closing check-ins must now be
invalidated with a status of unknown.

Part of GH-79328
Requires #79735
saponifi3d pushed a commit that referenced this pull request Nov 7, 2024
This causes clock ticks with the "volume_anomaly_result" set as abnormal
to dispatch a mark_unknown task instead of a check_timeouts task.

This is needed since when we detect an anomalous tick we're unable to
know if we lost customer data during that tick, meaning all in-progress
check-ins that were waiting for closing check-ins must now be
invalidated with a status of unknown.

Part of GH-79328
Requires #79735
@github-actions github-actions bot locked and limited conversation to collaborators Nov 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants