Thank you for the quick answer, I would be very happy to be able to upload the TraceDatasets. But currently it would be sufficient to start phoenix loading the trace_dataset from file system. However that does not work and I believe the problem lies in me using phoenix from docker. Here is the problem:
docker starts the server/main.py with the provided arguments with a start command provided through "CMD" inside the Dockerfile. Now I modified the usage via my own Dockerfile, so it would support the embeddings I would provide (named "wv_dump"). Afterwards I added "--trace" as next argument and I tried starting the docker with different names for traces:
the name inside the "TraceDataset" as argument: "mongo_traces"
the uuid generated for the trace dataset "e62dbee1-fb4f-422c-85d9-ca28695b72da"
simply to exclude, that that might function, I also tried: trace_dataset
Here is my Dockerfile:
FROM arizephoenix/phoenix:latest
ENTRYPOINT ["python", "-m", "phoenix.server.main",\
"--host", "0.0.0.0", "--port", "6006",\
"--enable-prometheus", "True",\
"datasets", "--primary", "wv_dump", "--trace", "f5a67854-cb20-4465-b13d-897b19a6cff8"]
# also tried mongo_traces and trace_dataset
The default entrypoint command inside Docker I have looked up here:
https://hub.docker.com/layers/arizephoenix/phoenix/latest/images/sha256-2a574eb6467e[…]a4acce2d13cc9aaf9925a4214896bd47ac8cb9f7636d6?context=explore
Afterwards I looked inside the code of the main.py inside "src/phoenix/server" and it seems to me, that the "--trace" argument is not even used inside the subparser "datasets" anywhere. Can we fix that?