-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
feat(aci): Write to IncidentGroupOpenPeriod #97906
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
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
bb6a301
WIP
snigdhas c352fe4
Write to IncidentOpenPeriod
snigdhas 9aaae00
Fix tests
snigdhas c6f4a41
Fix types
snigdhas bd0a843
Switch to with_feature
snigdhas 7b9a8f6
nits
snigdhas 70780e5
Fix types
snigdhas 4c1f95a
Address code review comments
snigdhas 94d00ff
Switch to using detector_id for the lookups
snigdhas b4b728c
Fix types
snigdhas cd0b7f9
feature flag and pass list of projects instead of queryset
ceorourke File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential bug: The call to
AlertRuleDetector.objects.get()
lacks error handling, which will cause a server crash if the object does not exist, breaking issue ingestion.Description: The method
create_from_occurrence
callsAlertRuleDetector.objects.get(detector_id=detector_id)
without handling theAlertRuleDetector.DoesNotExist
exception. Thedetector_id
value, derived fromoccurrence.evidence_data
, can be missing or invalid. Other parts of the codebase, such as insrc/sentry/incidents/grouptype.py
, consistently wrap similar queries intry...except
blocks, establishing a pattern that this is a known and expected failure case. An unhandledDoesNotExist
exception will propagate up the call stack, causing a server crash during the critical issue ingestion process.Suggested fix: Wrap the
AlertRuleDetector.objects.get()
call in atry...except AlertRuleDetector.DoesNotExist
block. In theexcept
block, log a warning and handle the case gracefully, for example by settingalert_id
toNone
and allowing execution to continue. This matches established patterns elsewhere in the codebase.severity: 0.85, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.