Skip to main content

​
Launch Phoenix

Run Phoenix on your own infrastructure, backed by PostgreSQL so traces persist beyond a single process. This is the option to reach for once Phoenix is shared across a team or environment.The self-hosting guide covers Kubernetes, Helm, Railway, AWS CloudFormation, Google Cloud Run, Azure, and Render, plus authentication and configuration.
Phoenix serves its UI and OTLP HTTP on port 6006, and OTLP gRPC on port 4317. For a local instance that’s http://localhost:6006 — leave it running while you work.
Dify connects to Phoenix over the network, so it needs the endpoint you just started — and an API key if the instance requires one.
Pointing at a deployment with authentication enabled? Set PHOENIX_COLLECTOR_ENDPOINT to that deployment’s hostname and PHOENIX_API_KEY to an API key from its Settings page. A local phoenix serve needs neither.

​
Connect Dify and Phoenix

To configure Phoenix tracing in your Dify application:
  1. Open the Dify application you want to monitor.
  2. In the left sidebar, navigate to Monitoring.
  3. On the Monitoring page, select Phoenix in the Tracing drop down to begin setup.
  4. Enter your Phoenix credentials and save. You can verify the monitoring status on the current page.

​
Observe

View Dify traces in Phoenix. Get rich details into tool calls, session data, workflow steps, and more.

​
Resources