fix(alerts): Delete all timestamps when omitted#6528
Closed
an8kk wants to merge 1 commit into
Closed
Conversation
Allow alert delete requests to omit lastReceived and mark every timestamp for the fingerprint as deleted. Keep the existing single timestamp behavior when lastReceived is provided. Fixes #2817
dosubot
Bot
added
the
size:M
|
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Allow alert delete requests to omit lastReceived and mark every timestamp for the fingerprint as deleted.
This keeps the existing single timestamp behavior when lastReceived is provided while supporting full alert deletion through one API call. When lastReceived is omitted, the route now fetches all alert history for the fingerprint without a result cap and applies the delete enrichment to each timestamp.
Fixes #2817