Managing Data Scalability in Phoenix with Retention Policies
I wonder how scalable phoenix is given it's using postgres and tracing can create lots of data. It feels periodically removing old data from postgres would be key for sustainability. I see
In Phoenix 9.0 or greater you will be able to automatically purge traces from projects by configuring a retention policy. Retention policies can be either time based or trace count based. Stay tuned for the 9.0 release.
on https://docs.arize.com/phoenix/settings/data-retention, is there ETA for when 9.0 would be available? Before 9.0, what would be the recommended way to keep data size under control e.g.
having a cron job to remove older data periodically by calling some phoenix APIs?
Any guidance on which APIs to call for data removal?
