Request for Permalink Support by Trace ID and Project Name

·May 09, 2025 05:41 AM

Hi friends, is it possible to support a permalink to the trace / span / session by the ID and project name? For example, path /projects/<url-encoded-project-name>/traces/<trace-id> should resolve, vs requiring us to obtain the project id upfront.

6 comments

· Sorted by Oldest

RunLLM
APP
·
Yes, Phoenix now supports identifying projects by both project ID and project name in REST API paths, including for permalinks. You can use `/projects/<project-name> /traces/<trace-id> ` as long as the project name does not contain `/`, `?`, or `#` characters. This is documented in the <https://docs.arize.com/phoenix/sdk-api-reference/projects|Phoenix REST API reference> and was implemented in <https://github.com/Arize-ai/phoenix/pull/7064|PR #7064>. If you use the project name in the path, Phoenix will resolve it to the correct project, so you do not need to obtain the project ID upfront. Just ensure the project name is URL-safe and meets the character restrictions. Sources: - <https://github.com/Arize-ai/phoenix/pull/7064|GitHub PR: allow project name as identifier in REST path> - <https://docs.arize.com/phoenix/sdk-api-reference/projects|Phoenix REST API reference>
💡 Hint: Mention RunLLM in the thread for followups.
Jo P.
·
So the v1 api GET request works based on the documentation above. Could we also have the dashboard URL work?
Jo P.
·
The use case is to link the Phoenix trace permalink in our own application. Without making additional v1 REST API requests phoenix, we'd only have the trace ID and project name handy.
Jo P.
·
Hi 🔒[private user]: we are self hosting
Mikyo
·
Hey Jo P. - we have a related ticket. Pretty common ask https://github.com/Arize-ai/phoenix/issues/6934 Just been heads down on some feature work. Please upvote and provide feedback! We definitely work on the backlog based on user demand!
Jo P.
·
Thank you Mikyo! Just upvoted!
1