> ## Documentation Index
> Fetch the complete documentation index at: https://docs.idun-group.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Arize Phoenix

> Set up Arize Phoenix observability to trace, evaluate, and troubleshoot your agents.

Set up Arize Phoenix to trace agent execution and view performance data in your Phoenix dashboard.

<Tip>
  Before starting, complete the [quickstart guide](/quickstart) to have an agent running on Idun Engine.
</Tip>

## Set up Phoenix observability

<Steps>
  <Step title="Get your Phoenix details">
    <Tabs>
      <Tab title="Phoenix Cloud">
        1. Go to [Arize Phoenix](https://phoenix.arize.com)
        2. Sign up or log in to your account
        3. Create a new project or select an existing one
        4. Note your **Project Name** and the **Collector Endpoint** (typically `https://collector.phoenix.com`)
      </Tab>

      <Tab title="Self-hosted">
        If you are hosting Phoenix yourself, have your collector endpoint URL ready. This is the URL where your Phoenix instance accepts trace data.
      </Tab>
    </Tabs>
  </Step>

  <Step title="Configure Phoenix in the standalone">
    Open the running standalone at `/admin/observability/` and click **Phoenix**. Fill in:

    * **Collector endpoint**: URL of the Phoenix collector (e.g., `https://collector.phoenix.com` or your self-hosted URL)
    * **Project name**: The project in Phoenix to bucket these traces under

    <Frame>
      <img src="https://mintcdn.com/idunlabs/SjVPzIbyPaldjUKK/images/ui/admin-observability-phoenix.png?fit=max&auto=format&n=SjVPzIbyPaldjUKK&q=85&s=9903bc9b9cb9f539c13538f07a2212b3" alt="Observability admin page with Phoenix selected" width="1911" height="1040" data-path="images/ui/admin-observability-phoenix.png" />
    </Frame>

    Save the form. The reload pipeline re-instantiates the engine with the new observability config; the next agent run starts streaming spans to Phoenix.
  </Step>
</Steps>

Alternatively, configure Phoenix in your `config.yaml` for first-boot seeding or engine-only mode:

```yaml config.yaml theme={"theme":{"light":"github-light","dark":"github-dark"}}
observability:
  - provider: "PHOENIX"
    enabled: true
    config:
      collector_endpoint: "https://collector.phoenix.com"
      project_name: "idun-agent"
```

## View observability data

Once your agent is running with observability enabled:

1. Interact with your agent through the chat UI at `/` or the API at `/agent/run`
2. Open your Phoenix dashboard
3. Navigate to your project to view traces

You will see traces showing agent execution flows, tool usage, and latency data.

## Best practices

* Use descriptive names for observability configurations
* Monitor latency using Phoenix's performance tools
* Check traces regularly to understand agent behavior

## Troubleshooting

<Warning>
  ADK does not currently support simultaneous tracing with multiple providers.
</Warning>

<AccordionGroup>
  <Accordion title="Observability not working?">
    1. **Check collector endpoint**: Verify the URL is correct and accessible from the agent environment
    2. **Verify project name**: Confirm it matches the project name in Phoenix exactly
    3. **Check network**: Confirm your agent environment can reach the Phoenix collector
  </Accordion>
</AccordionGroup>

## Next steps

<Card title="Local trace store" icon="database" horizontal href="/observability/traces">
  See the same agent runs in the bundled admin UI without extra config.
</Card>

<Card title="Observability overview" icon="chart-line" horizontal href="/observability/overview">
  Compare built-in providers and their configuration shapes.
</Card>

<Card title="Custom handler" icon="puzzle" horizontal href="/observability/custom-handler">
  Wire a different OTel-compatible backend through Pattern B.
</Card>