Arize link
Build clickable Arize UI URLs from exported IDs, logs, or existing browser URLs by validating base64 path IDs, selecting the right resource template, and preserving or computing trace time windows.
When to invoke
- "Create an Arize link for this trace ID."
- "Open this span in Arize."
- "Give me a URL for this dataset."
- "Link to the labeling queue."
- "Share the evaluator version in Arize."
Inputs
| Resource |
Required inputs |
Optional inputs |
| Trace |
org_id, space_id, project_id, trace_id, startA, endA |
span_id, base_url |
| Span |
org_id, space_id, project_id, trace_id, span_id, startA, endA |
base_url |
| Session |
org_id, space_id, project_id, session_id, startA, endA |
base_url |
| Dataset |
org_id, space_id, dataset_id |
`selectedTab=examples |
| Queue list |
org_id, space_id |
base_url |
| Specific queue |
org_id, space_id, queue_id |
base_url |
| Evaluator |
org_id, space_id, evaluator_id |
version, base_url |
| Annotation configs |
org_id, space_id |
base_url |
Default base_url is https://app.arize.com; override it only for on-prem deployments.
ID validation
All path IDs must be base64-encoded with characters A-Za-z0-9+/=. Raw numeric IDs produce valid-looking URLs that 404. If the user provides a number, ask them to copy the ID directly from an Arize browser URL such as https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…. If a raw internal ID is available, such as Organization:1:abC1, base64-encode it before inserting it into the URL.
URL templates
| Resource |
Template |
| Trace |
{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}?selectedTraceId={trace_id}&queryFilterA=&selectedTab=llmTracing&timeZoneA=America%2FLos_Angeles&startA={start_ms}&endA={end_ms}&envA=tracing&modelType=generative_llm |
| Span highlight |
Append &selectedSpanId={span_id} to the trace URL. |
| Session |
{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}?selectedSessionId={session_id}&queryFilterA=&selectedTab=llmTracing&timeZoneA=America%2FLos_Angeles&startA={start_ms}&endA={end_ms}&envA=tracing&modelType=generative_llm |
| Dataset examples |
{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=examples |
| Dataset experiments |
{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=experiments |
| Queue list |
{base_url}/organizations/{org_id}/spaces/{space_id}/queues |
| Specific queue |
{base_url}/organizations/{org_id}/spaces/{space_id}/queues/{queue_id} |
| Evaluator latest |
{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id} |
| Evaluator version |
{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}?version={version_url_encoded} |
| Annotation configs |
{base_url}/organizations/{org_id}/spaces/{space_id}/annotation-configs |
URL-encode version; for example, a trailing = becomes %3D.
Time range rules
startA and endA are required epoch milliseconds for trace, span, and session links. Omitting them defaults to the last 7 days and can show "no recent data" when the trace falls outside that window.
| Priority |
Source |
Rule |
| 1 |
User-provided URL |
Extract and reuse startA and endA directly. |
| 2 |
Span start_time |
Pad by ±1 day, or ±1 hour for a tighter window. |
| 3 |
Fallback |
Use last 90 days: now - 90d to now. |
Prefer tight windows because 90-day windows load slowly.
Procedure
- Gather IDs from the user, exported trace data, logs, or an existing Arize URL.
- Validate
org_id, space_id, and other path IDs as base64.
- Determine
startA and endA for trace/span/session links using the priority order.
- Select the resource template and URL-encode query values such as evaluator
version.
- Present a clickable Markdown link.
Troubleshooting
| Symptom |
Likely cause |
Resolution |
| "No data" or empty view |
Trace outside time window |
Widen startA/endA: ±1h -> ±1d -> 90d. |
| 404 |
Wrong ID or non-base64 ID |
Re-check org_id, space_id, and project_id from the browser URL. |
| Span not highlighted |
span_id belongs to a different trace |
Verify span_id against exported span data. |
org_id unknown |
ax CLI does not expose it |
Ask the user to copy it from https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…. |
Progressive disclosure and bundled resources
references/EXAMPLES.md: concrete URLs for every supported Arize link type.
Related primitives
| Name |
Type |
Use it when |
arize-trace |
skill |
You need to export spans to obtain trace_id, span_id, or start_time before linking. |
The trace/span path uses trace/span inputs. selectedTab accepts examples or experiments. Evaluator versions may appear as ?version=…. Treat missing time range as CRITICAL. Preserve the raw-ID note: ). If you have a raw internal ID (e.g. .
Output template
## Arize link result
**Status:** linked | blocked
**Resource:** `trace | span | session | dataset | queue | evaluator | annotation-configs`
[Open in Arize](<generated URL>)
### Inputs used
- `org_id`: `<base64 id>`
- `space_id`: `<base64 id>`
- Resource ID: `<id>`
- Time range: `<startA>-<endA or not required>`
Quality gate
References
1---2name: arize-link-23description: Generate Arize UI deep links for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs using base64 org and space IDs, resource IDs, and trace/session time windows. Use when the user wants to link to, open, share, or debug an Arize trace, span, session, dataset, queue, evaluator, or annotation config.4---56# Arize link78Build clickable Arize UI URLs from exported IDs, logs, or existing browser URLs by validating base64 path IDs, selecting the right resource template, and preserving or computing trace time windows.910## When to invoke1112- "Create an Arize link for this trace ID."13- "Open this span in Arize."14- "Give me a URL for this dataset."15- "Link to the labeling queue."16- "Share the evaluator version in Arize."1718## Inputs1920| Resource | Required inputs | Optional inputs |21| --- | --- | --- |22| Trace | `org_id`, `space_id`, `project_id`, `trace_id`, `startA`, `endA` | `span_id`, `base_url` |23| Span | `org_id`, `space_id`, `project_id`, `trace_id`, `span_id`, `startA`, `endA` | `base_url` |24| Session | `org_id`, `space_id`, `project_id`, `session_id`, `startA`, `endA` | `base_url` |25| Dataset | `org_id`, `space_id`, `dataset_id` | `selectedTab=examples|experiments`, `base_url` |26| Queue list | `org_id`, `space_id` | `base_url` |27| Specific queue | `org_id`, `space_id`, `queue_id` | `base_url` |28| Evaluator | `org_id`, `space_id`, `evaluator_id` | `version`, `base_url` |29| Annotation configs | `org_id`, `space_id` | `base_url` |3031Default `base_url` is `https://app.arize.com`; override it only for on-prem deployments.3233## ID validation3435All path IDs must be base64-encoded with characters `A-Za-z0-9+/=`. Raw numeric IDs produce valid-looking URLs that 404. If the user provides a number, ask them to copy the ID directly from an Arize browser URL such as `https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…`. If a raw internal ID is available, such as `Organization:1:abC1`, base64-encode it before inserting it into the URL.3637## URL templates3839| Resource | Template |40| --- | --- |41| Trace | `{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}?selectedTraceId={trace_id}&queryFilterA=&selectedTab=llmTracing&timeZoneA=America%2FLos_Angeles&startA={start_ms}&endA={end_ms}&envA=tracing&modelType=generative_llm` |42| Span highlight | Append `&selectedSpanId={span_id}` to the trace URL. |43| Session | `{base_url}/organizations/{org_id}/spaces/{space_id}/projects/{project_id}?selectedSessionId={session_id}&queryFilterA=&selectedTab=llmTracing&timeZoneA=America%2FLos_Angeles&startA={start_ms}&endA={end_ms}&envA=tracing&modelType=generative_llm` |44| Dataset examples | `{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=examples` |45| Dataset experiments | `{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=experiments` |46| Queue list | `{base_url}/organizations/{org_id}/spaces/{space_id}/queues` |47| Specific queue | `{base_url}/organizations/{org_id}/spaces/{space_id}/queues/{queue_id}` |48| Evaluator latest | `{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}` |49| Evaluator version | `{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}?version={version_url_encoded}` |50| Annotation configs | `{base_url}/organizations/{org_id}/spaces/{space_id}/annotation-configs` |5152URL-encode `version`; for example, a trailing `=` becomes `%3D`.5354## Time range rules5556`startA` and `endA` are required epoch milliseconds for trace, span, and session links. Omitting them defaults to the last 7 days and can show "no recent data" when the trace falls outside that window.5758| Priority | Source | Rule |59| --- | --- | --- |60| 1 | User-provided URL | Extract and reuse `startA` and `endA` directly. |61| 2 | Span `start_time` | Pad by ±1 day, or ±1 hour for a tighter window. |62| 3 | Fallback | Use last 90 days: `now - 90d` to `now`. |6364Prefer tight windows because 90-day windows load slowly.6566## Procedure67681. Gather IDs from the user, exported trace data, logs, or an existing Arize URL.692. Validate `org_id`, `space_id`, and other path IDs as base64.703. Determine `startA` and `endA` for trace/span/session links using the priority order.714. Select the resource template and URL-encode query values such as evaluator `version`.725. Present a clickable Markdown link.7374## Troubleshooting7576| Symptom | Likely cause | Resolution |77| --- | --- | --- |78| "No data" or empty view | Trace outside time window | Widen `startA`/`endA`: ±1h -> ±1d -> 90d. |79| 404 | Wrong ID or non-base64 ID | Re-check `org_id`, `space_id`, and `project_id` from the browser URL. |80| Span not highlighted | `span_id` belongs to a different trace | Verify `span_id` against exported span data. |81| `org_id` unknown | `ax` CLI does not expose it | Ask the user to copy it from `https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…`. |8283## Progressive disclosure and bundled resources8485- `references/EXAMPLES.md`: concrete URLs for every supported Arize link type.8687## Related primitives8889| Name | Type | Use it when |90| --- | --- | --- |91| `arize-trace` | skill | You need to export spans to obtain `trace_id`, `span_id`, or `start_time` before linking. |9293The trace/span path uses `trace/span` inputs. `selectedTab` accepts `examples` or `experiments`. Evaluator versions may appear as `?version=…`. Treat missing time range as `CRITICAL`. Preserve the raw-ID note: `). If you have a raw internal ID (e.g. `.9495## Output template9697```markdown98## Arize link result99100**Status:** linked | blocked101**Resource:** `trace | span | session | dataset | queue | evaluator | annotation-configs`102103[Open in Arize](<generated URL>)104105### Inputs used106- `org_id`: `<base64 id>`107- `space_id`: `<base64 id>`108- Resource ID: `<id>`109- Time range: `<startA>-<endA or not required>`110```111112## Quality gate113114- [ ] `org_id` and `space_id` are base64 path IDs, not raw numeric IDs.115- [ ] The selected URL template matches the requested resource.116- [ ] Trace, span, and session links include `startA` and `endA` in epoch milliseconds.117- [ ] Existing `startA` and `endA` values from a user-provided URL were preserved when available.118- [ ] Evaluator `version` was URL-encoded when present.119- [ ] The final answer includes a clickable Markdown link.120121## References122123- [Arize application](https://app.arize.com)
paulasilvatech