Backup daily events in the Redis migrations
What does this MR do and why?
We're getting rid of :aggregation
param for events. The only place where we keep using it is older Redis key migration.
These migrations were executed on Saas and ~20% of SM instances, but not all. We can't loose data from those unmigrated instances and can't just drop old migrations.
The solution is to back-up daily events (its a small subset of events and no new events getting added anymore) to be able to not take this dependency during known_events
removal process
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #387785 (closed)