> This page is for NeMo Relay, version dev.
> For other versions, use one of these documentation indexes:
> - Latest (v0.11.2) (default): https://docs.nvidia.com/nemo/relay/latest/llms.txt
> - dev: https://docs.nvidia.com/nemo/relay/dev/llms.txt
> - v0.11.2: https://docs.nvidia.com/nemo/relay/v0.11.2/llms.txt
> - v0.10.4: https://docs.nvidia.com/nemo/relay/v0.10.4/llms.txt
> - v0.9.4: https://docs.nvidia.com/nemo/relay/v0.9.4/llms.txt
> - v0.8.4: https://docs.nvidia.com/nemo/relay/v0.8.4/llms.txt
> - v0.7.3: https://docs.nvidia.com/nemo/relay/v0.7.3/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/relay/llms.txt.

# Connect to Phoenix

> Export Relay OpenInference traces to Phoenix and confirm agent, model, and tool spans.

Use the [shared capture and verification path](/nemo/relay/dev/user-guides/connecting-to-observability-platforms)
to send a run captured by [NVIDIA NeMo Relay](https://github.com/NVIDIA/NeMo-Relay)
to [Arize Phoenix](https://arize.com/phoenix/). Phoenix receives
[OpenTelemetry](https://opentelemetry.io/) traces; Relay supplies the agent,
model, and tool spans it captured. Use the
`openinference` projection so Phoenix can identify those span roles.

> **Use the same companion workload**
>
> Select `--destination phoenix` in the parent guide's example. Start a local Phoenix instance, or supply its remote trace URL and required authorization. The loopback endpoint is the default.
> Find service `relay-support-triage` and apply this page's destination checks.

## Start a local Phoenix instance

For a disposable local backend, run this in a separate terminal and keep it open:

```bash
PHOENIX_HOST=127.0.0.1 uvx --from arize-phoenix==21.0.0 phoenix serve
```

The UI and HTTP trace intake use port `6006` by default. Follow the
[Phoenix terminal deployment instructions](https://arize.com/docs/phoenix/self-hosting/deployment-options/terminal)
for a persistent installation. For a remote VM, forward the port as described
in the parent guide; an unauthenticated Phoenix UI should stay on a trusted host.

## Point the worker or application at Phoenix

Choose the tracing intake URL for your Phoenix Cloud space or self-hosted
instance. The address used to open the Phoenix UI may differ from the OTLP
intake URL. The following `plugins.toml` example shows a remote HTTPS intake;
replace the illustrative host with your deployment's complete trace URL.

```toml
version = 1

[[components]]
kind = "observability"
enabled = true

[components.config]
version = 4

[components.config.opentelemetry]
enabled = true

[[components.config.opentelemetry.endpoints]]
type = "openinference"
endpoint = "https://phoenix.example.com/v1/traces"
transport = "http_binary"
service_name = "relay-support-triage"

[components.config.opentelemetry.endpoints.resource_attributes]
"openinference.project.name" = "relay-support-triage"

[components.config.opentelemetry.endpoints.header_env]
authorization = "PHOENIX_AUTHORIZATION"
```

Set `PHOENIX_AUTHORIZATION` in the Relay worker or application environment to
the full `Bearer <api-key>` header value when the intake requires an API key.
For an unauthenticated loopback Phoenix instance, omit `header_env` and use
that instance's local trace URL. Keep the credential outside the config file.
Phoenix documents its [endpoint choices](https://arize.com/docs/phoenix/learn/faqs/what-is-my-phoenix-endpoint)
and [authentication header](https://arize.com/docs/phoenix/deployment/authentication).

## Check a complete trace

The companion's `--verify` option checks delivered spans through the Phoenix
API. Also inspect the trace tree below to confirm its structure and useful fields.

In the `relay-support-triage` Phoenix project, find the test run by time and service name.
Open its trace tree and check the following evidence:

| Check               | Expected result                                                                              |
| ------------------- | -------------------------------------------------------------------------------------------- |
| Agent parent        | The run has a recognizable top-level agent or turn span when the capture path emits one.     |
| Model and tool work | Calls observed by Relay are children or related spans in the same trace.                     |
| Privacy             | Restricted prompt or tool fields are absent or transformed according to the approved policy. |

If no trace appears, first check the intake URL, authorization, and reachability
from the actual Relay process. If only model or tool activity is missing,
confirm that those calls crossed the Relay capture boundary. The
[Observability reference](/nemo/relay/dev/configure-plugins/observability/configuration)
provides exporter delivery diagnostics.

## Recognize the example trace

The parent guide's [expected trace](/nemo/relay/dev/user-guides/connecting-to-observability-platforms#expected-trace)
shows the Hermes workload's agent, model, and tool activity. Use it when running
that example; match your own deployment's captured scopes and parentage when
using another integration.