Log Rotation for Phoenix App in Docker: Challenges & Solutions
Hey Arize Team! I wanted to ask if there is a way to log rotate the trace datasets from my docker container that is running phoenix app (We have a separate application hosted elsewhere that sends trace data to this phoenix server in a docker container) I know there is a api to get trace data from the phoenix client but this leads to unpredictable and bursty demand for resources (CPU, I/O, Memory, etc). We instead wanted to rotate the underlying log files ourselves and have it be stored elsewhere I found the working directory within my docker container /root/.phoenix but it contains 3 empty directories datasets, exports, and trace_datasets with no files inside it. Though my phoenix server is showing 23 traces Few clarifying questions
- 1.
Is all the trace data actually stored in the above directory? Or is there some other one, or are these directories not used the way i thought they were?
- 2.
Is the above alternative to get_spans_dataframe a good one? any challenges you think (pending 1 is actually how I think about it)
Any help here would be much appreciated, without log rotation, we are having a hard time maintaining the server running phoenix in a production setting
