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

Configuring PHOENIX_COLLECTOR_ENDPOINT for Arize Phoenix | Arize AI Community

Phoenix Support

Configuring PHOENIX_COLLECTOR_ENDPOINT for Arize Phoenix

·Dec 01, 2023 02:44 PM

Ciao Luca B.! You can do this by configuring the following the environment variable PHOENIX_COLLECTOR_ENDPOINT to point to the server running in a different process or container. https://docs.arize.com/phoenix/environments

9 comments

· Sorted by Oldest

Luca B.
·
will try this out and come back if I have questions - thanks in the meantime!
Luca B.
·
Hey there! I am not using OpenAI to work with phoenix, is there a way for me to write my own instrumentor? I already have a wrapper for llamaindex. https://docs.arize.com/phoenix/environments#container
Mikyo
·
Hey Luca! You certainly could! You are looking to trace things that wrap LlamaIndex? What are you looking to instrument? If so you can certainly publish your own spans via the tracer - We are definitely going to support more custom instrumentation but let us know if you hit any walls! https://github.com/Arize-ai/phoenix/blob/main/src/phoenix/trace/tracer.py

·

Thanks again for the reply! I found what I needed by inspecting the source code in llamaindex:

from phoenix.trace.exporter import HttpExporter
import llama_index

os.environ["PHOENIX_COLLECTOR_ENDPOINT"] = "http://0.0.0.0:6006"

exporter = HttpExporter(endpoint="http://0.0.0.0:6006")
llama_index.set_global_handler("arize_phoenix", exporter=exporter)

Luca B.
·
This should configure phoenix as global handler and export the traces to the UI running in a different process (e.g.a container)
Mikyo
·
Awesome! Glad you figured that out :)
Luca B.
·
Would you like to add this to your documentation? I could help if you wanted.
Mikyo
·
Oh that would be awesome! Yeah anything that helps with this would be very much appreciated!
👀1
Luca B.
·
Will ping you know later this week (bit busy with PyData Global tonight).