chore(anomaly-detection): do not store data if operation takes too long #1701
Conversation
This file contains 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
ram-senth
force-pushed
the
anomaly_detection/abandon_long_running
branch
5 times, most recently
from
27f8e11 to
723bee1
Compare
ram-senth
force-pushed
the
anomaly_detection/abandon_long_running
branch
from
723bee1 to
a666cae
Compare
aayush-se
approved these changes
Jan 9, 2025
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change aborts saving data if the batch detection takes too long. This will help reduce the instances when Seer data goes out of sync with alerting system.
With this implementation, both
store_dataanddetect_anomaliesAPIs return 500 - server error if the detection takes longer than 4.5 mins.