Connect to Phoenix
Use the shared capture and verification path
to send a run captured by NVIDIA NeMo Relay
to Arize Phoenix. Phoenix receives
OpenTelemetry traces; Relay supplies the agent,
model, and tool spans it captured. Use the
openinference projection so Phoenix can identify those span roles.
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:
The UI and HTTP trace intake use port 6006 by default. Follow the
Phoenix terminal deployment instructions
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.
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
and authentication header.
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:
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 provides exporter delivery diagnostics.
Recognize the example trace
The parent guide’s 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.