Is your feature request related to a problem? Please describe.
We were testing the use of the tool in the past couple of weeks. It seems like there is no way to completely delete alerts/workflow execution logs/etc in a way, where they are also removed from the database. Right now, it seems like the database is growing forever. This is not something, that's possible to maintain on a long term.
Describe the solution you'd like
Implement a way to delete alerts and other data that has the ability to grow the database significantly.
Describe alternatives you've considered
Deleting data from the database manually. This is wrong for obvious reasons. What happens if migrations update the structure in the future? What if something gets corrupted?
Additional context
We've been using KeepHQ for about a month and our postgres database is at ~20GB already.
(Regardless of how many alerts are sent in different environments, eventually every instance would grow out of a reasonable sized database.)
Is your feature request related to a problem? Please describe.
We were testing the use of the tool in the past couple of weeks. It seems like there is no way to completely delete alerts/workflow execution logs/etc in a way, where they are also removed from the database. Right now, it seems like the database is growing forever. This is not something, that's possible to maintain on a long term.
Describe the solution you'd like
Implement a way to delete alerts and other data that has the ability to grow the database significantly.
Describe alternatives you've considered
Deleting data from the database manually. This is wrong for obvious reasons. What happens if migrations update the structure in the future? What if something gets corrupted?
Additional context
We've been using KeepHQ for about a month and our postgres database is at ~20GB already.
(Regardless of how many alerts are sent in different environments, eventually every instance would grow out of a reasonable sized database.)