arize-link

1# Arize Link
2 
3Generate deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs.
4 
5## When to Use
6 
7- User wants a link to a trace, span, session, dataset, labeling queue, evaluator, or annotation config
8- You have IDs from exported data or logs and need to link back to the UI
9- User asks to "open" or "view" any of the above in Arize
10 
11## Required Inputs
12 
13Collect from the user or context (exported trace data, parsed URLs):
14 
15| Always required | Resource-specific |
16|---|---|
17| `org_id` (base64) | `project_id` + `trace_id` [+ `span_id`] — trace/span |
18| `space_id` (base64) | `project_id` + `session_id` — session |
19| | `dataset_id` — dataset |
20| | `queue_id` — specific queue (omit for list) |
21| | `evaluator_id` [+ `version`] — evaluator |
22 
23**All path IDs must be base64-encoded** (characters: `A-Za-z0-9+/=`). A raw numeric ID produces a valid-looking URL that 404s. If the user provides a number, ask them to copy the ID directly from their Arize browser URL (`https://app.arize.com/organizations/{org_id}/spaces/{space_id}/…`). If you have a raw internal ID (e.g. `Organization:1:abC1`), base64-encode it before inserting into the URL.
24 
25## URL Templates
26 
27Base URL: `https://app.arize.com` (override for on-prem)
28 
29**Trace** (add `&selectedSpanId={span_id}` to highlight a specific span):
30```
31…