Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Phoenix Support

Phoenix Data Flushing: Options for Persistence Without Deletion | Arize AI Community

Phoenix Support

Phoenix Data Flushing: Options for Persistence Without Deletion

·Apr 23, 2024 03:07 PM

Stijn D. moving your Phoenix support question here:

Xander S. while working on the persistence support, what options do we now have wrt flushing data out of phoenix, but not completely deleting it?

13 comments

· Sorted by Oldest

Tammy L.
·
is there a way to eg save traces older then X days to file and flush them from the runnning instance? some variation on https://docs.arize.com/phoenix/tracing/how-to-tracing/save-and-load-traces#create-directory-and-save-traces i presume? the idea would be to run a daily cron job that flushes out anything older then eg 7 days
Roger Y.
·
we have not settled on the specifics but this has come up in discussion
Roger Y.
·
it’s on our roadmap as a feture
Roger Y.
·
we can extract the traces, but currently they cannot be removed from phenix
Stijn D.
·
thanks for the reply.
Stijn D.
·
so what are our options to keep the memory usage in check?
Stijn D.
·
save trace, restart phoenix and load the latest traces?
Stijn D.
·
what syntax can i use to only save the last X traces?
Roger Y.
·
save trace, restart phoenix and load the latest traces?
yes, this is the workaround for now
what syntax can i use to only save the last X traces?
we don’t have any syntax for that right now
Roger Y.
·
we only have a time range filter (start_time and stop_time) on the Client.get_spans_dataframe and Client.query_spans functions
Stijn D.
·
ok, that will also work
Stijn D.
·
looking forward to have this properly supported (will probably be less of an issue once persistency is added 😉
Roger Y.
·
yea, with persistence this is all moot