Just curious at this point -
I have a use case where I’ll have … a lot of events. So many that every 12 hours ES consumes ~200gb.
Are there any strategies / features I could use to “archive” old events I know will rarely be read back? Kind of like how graphite compresses old metric data to conserve disk space.
Right now I am toying with an idea to use a separate storage for a certain type of event that I know will decrease disk usage significantly - but it makes things much more complicated (distributed transactions)