Hello! We have a self hosted phoenix-client in azure that is redirected through a proxy so the root path is /monitoring. We are correctly doing
- name: PHOENIX_HOST_ROOT_PATH
value: /monitoringto change it as env variable during deployment but when we press the button share in a trace the output given doesn't contain the root path so when sharing with another people of the team they have to enter the phoenix an search for the trace or add the /monitoring by hand. Is it a problem with the current phoenix-client implementation or should we add another env variable/make any changes?
The PHOENIX_HOST_ROOT_PATH environment variable is the correct way to set a root path prefix (e.g., /monitoring) for Phoenix when running behind a reverse proxy. However, for share links and other URLs to include this prefix automatically, you must also set the PHOENIX_ROOT_URL environment variable to the full external URL (including the root path), such as https://your-domain.com/monitoring. Setting only PHOENIX_HOST_ROOT_PATH is not enough鈥擯hoenix uses PHOENIX_ROOT_URL to generate absolute URLs for sharing and callbacks [docs, config.py].So, add: LBKS- name: PHOENIX_ROOT_URL value: https://your-domain.com/monitoringLBKSto your deployment. This should ensure that all generated share links include the /monitoring prefix automatically.Would you like more detail on how Phoenix constructs URLs or how to verify this in your deployment?Sources:
- phoenix/config.py (ENV_PHOENIX_ROOT_URL)
- docs
馃挕聽Hint: Mention RunLLM in the thread for followups.
hey Alejandro E. good catch. That's an oversight on our URL construction. Will get it fixed with Yasmine F. asap
Thank you so much!
Hi Alejandro E., thanks for bringing this to our attention. this should be fixed in v11.38.0. relevant PR: https://github.com/Arize-ai/phoenix/pull/9639 let us know if you encounter any other issues with this or anything else!
