CSOAR-4496 Atlassian OpsGenie integration problems #6263
Conversation
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
mahendrak-sumo
requested review from
JV0812,
amee-sumo,
jpipkin1,
kimsauce and
mafsumo
as code owners
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.
Purpose of this pull request
This PR addresses an issue where the Atlassian OpsGenie integration fails due to timing problems when checking request status immediately after alert creation. The fix implements a retry mechanism with exponential backoff to handle cases where the request status endpoint returns 404 errors because the request hasn't been fully processed yet.
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/CSOAR-4496