You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Production DB having millions of messages and jobs that are no longer required/relevant. This could also potentially be GBs of data that can be moved to cold storage
Describe the solution you'd like
We would want to design a command under webhook broker main process that would trigger a archival for dispatched messages and without any dead jobs. If there is even one dead job for the message would not be archived. We would also optionally provide a priorToDate to choose the messages and event, by default it would be a week prior to the command. The messages to be archived would be written against a cold storage (compared to DB) like AWS S3.
Describe alternatives you've considered
Manually dumping from the Database and deleting the rows.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Production DB having millions of messages and jobs that are no longer required/relevant. This could also potentially be GBs of data that can be moved to cold storage
Describe the solution you'd like
We would want to design a command under webhook broker main process that would trigger a archival for dispatched messages and without any dead jobs. If there is even one dead job for the message would not be archived. We would also optionally provide a
priorToDate
to choose the messages and event, by default it would be a week prior to the command. The messages to be archived would be written against a cold storage (compared to DB) like AWS S3.Describe alternatives you've considered
Manually dumping from the Database and deleting the rows.
Additional context
The text was updated successfully, but these errors were encountered: