accessing direct links to session data in phoenix cloud (agno instrumentation)

[adiberk]

Describe the bug
In phoenix cloud every trace seems to have a spanNodeID. Where does this id get set? I have my own observability setup and have access to both the trace_id and the span_id for every trace. However I am unable to set the spanNodeId with the right value

To Reproduce
spanNodeID doesn't seem to be a value available in the span information.

Expected behavior
I should have a way to use the information from my span to access a specific trace or subtrace (via trace_id anddspan)

I am using agno instrumentation!

[dosubot[bot]]

Hi @adiberk! I'm Dosu and I’m helping the openinference team.

spanNodeID in Phoenix Cloud is an internal global identifier for each span, separate from the standard OpenTelemetry trace_id and span_id. It is generated and managed by the Phoenix backend/database and is not available as a field in your span data or settable via agno instrumentation. There is no direct way to map or set spanNodeID using trace_id and span_id alone—it's used internally for navigation and linking in the UI and API, but not exposed or configurable from the client side. This means you can't construct direct links to session data using only trace_id and span_id in your current setup, which is a known limitation for custom observability pipelines using agno instrumentation.
Reference

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[adiberk]

Seems less specific to Agno but rather anyone using arize phoenix cloud?

I would make a request that maybe span id be used as the row/node identifier. Other services (logfire, datadog etc.) typically have ways of generator info links to traces/spans more directly.

[axiomofjoy]

Hey @adiberk, the IDs you are seeing are GraphQL node IDs rather than OTel IDs. In general, our routing uses these GraphQL node IDs as parameters. If you wish to view a span or trace by OTel ID, you can the routes at /redirects/spans/<span-otel-id> or /redirects/traces/<trace-otel-id>. Hope this helps!