What is the right way to deal with rapid growth in the side of the

event_log

table? As a result of a streaming/microbatch process we have started , the table grows by ~25GB a day, and it is getting to be quite large. Is there an official way to prune it?

Hi! Here's a GitHub Discussion that describes a pattern for cleaning up your Dagster database. https://github.com/dagster-io/dagster/discussions/12047

Is this also going to trigger the VACUUM and the like on the backed, or is that not needed/will happen automatically

Hmm, I actually don't know. Do you mind asking that in the discussion? I'll bump it over to someone closer to it on the team and we can persist that answer in the GitHub Discussion.

Posted, thanks