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): Skip marking unknowns as failures #80347

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

evanpurkhiser
Copy link
Member

When an UNKNOWN check-in is processed through mark_failure do NOT produce an issue occurance or do any incident creation.

This will be used by mark_missing to produce UNKNOWN check-ins during a possible data-loss incident, but not notify the user that their monitor was missed.

Part of GH-79328

@evanpurkhiser evanpurkhiser requested a review from a team as a code owner November 6, 2024 23:27
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 6, 2024
Copy link

codecov bot commented Nov 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #80347      +/-   ##
==========================================
+ Coverage   76.34%   78.34%   +1.99%     
==========================================
  Files        7191     7190       -1     
  Lines      318149   318142       -7     
  Branches    43856    43857       +1     
==========================================
+ Hits       242896   249250    +6354     
+ Misses      68584    62533    -6051     
+ Partials     6669     6359     -310     

@@ -55,7 +56,7 @@ def mark_failed(

# When the failed check-in is a synthetic missed check-in we do not move
# the `last_checkin` timestamp forward.
if failed_checkin.status == CheckInStatus.MISSED:
if is_miss:
Copy link
Member

Choose a reason for hiding this comment

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

i'm kind of confused why we need this boolean instead of relying on the checkin status

Copy link
Member Author

Choose a reason for hiding this comment

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

Because the check-in status will be UNKNOWN in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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