statusmgr: expire status subscriptions after 7 days #3610
Merged
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.
Description:
This PR updates the statusmgr to expire/delete alert status subscriptions after 7 days of inactivity.
Which issue(s) this PR fixes:
Closes #3245
Describe any introduced user-facing changes:
N/A
Describe any introduced API changes:
N/A
Additional Info:
A new
updated_at
column was added, and the engine will now update the timestamp each time a status update is processed. Rows whereupdated_at
is more than 7 days old are deleted/cleaned up, no longer requiring processing and no longer resulting in update messages.If an alert escalates and a new message is sent, a new subscription would be created and behave as it does today. Effectively this means you may receive updates to a notification alert for up to 7 days as an absolute maximum.
NOTE: Existing status subscriptions will be set to the current time, so the 7 day maximum will take effect in full 7 days after this update is deployed.