skilld
All skills
github avatar

/arize-link

@4e136f3 official
by githubgithub/awesome-copilot40k stars
5,040

Generates deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs. Produces clickable URLs for sharing Arize resources with team members. Use when the user wants to link to or open a trace, span, session, dataset, evaluator, or annotation config in the Arize UI.

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/arize-link

This session only. Nothing lands on disk.

SKILL.md

≈84 tokens always: the name and description. ≈1k when used: this file. ≈515 more on demand in 1 file.

Arize Link

Generate deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs.

When to Use

  • User wants a link to a trace, span, session, dataset, labeling queue, evaluator, or annotation config
  • You have IDs from exported data or logs and need to link back to the UI
  • User asks to "open" or "view" any of the above in Arize

Required Inputs

Collect from the user or context (exported trace data, parsed URLs):

Always required Resource-specific
org_id (base64) project_id + trace_id [+ span_id] — trace/span
space_id (base64) project_id + session_id — session
dataset_id — dataset
queue_id — specific queue (omit for list)
evaluator_id [+ version] — evaluator

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.

URL Templates

Base URL: https://app.arize.com (override for on-prem)

Trace (add &selectedSpanId={span_id} to highlight a specific span):

{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

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 (selectedTab: examples or experiments):

{base_url}/organizations/{org_id}/spaces/{space_id}/datasets/{dataset_id}?selectedTab=examples

Queue list / specific queue:

{base_url}/organizations/{org_id}/spaces/{space_id}/queues
{base_url}/organizations/{org_id}/spaces/{space_id}/queues/{queue_id}

Evaluator (omit ?version=… for latest):

{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}
{base_url}/organizations/{org_id}/spaces/{space_id}/evaluators/{evaluator_id}?version={version_url_encoded}

The version value must be URL-encoded (e.g., trailing = → %3D).

Annotation configs:

{base_url}/organizations/{org_id}/spaces/{space_id}/annotation-configs

Time Range

CRITICAL: startA and endA (epoch milliseconds) are required for trace/span/session links — omitting them defaults to the last 7 days and will show "no recent data" if the trace falls outside that window.

Priority order:

  1. User-provided URL — extract and reuse startA/endA directly.
  2. Span start_time — pad ±1 day (or ±1 hour for a tighter window).
  3. Fallback — last 90 days (now - 90d to now).

Prefer tight windows; 90-day windows load slowly.

Instructions

  1. Gather IDs from user, exported data, or URL context.
  2. Verify all path IDs are base64-encoded.
  3. Determine startA/endA using the priority order above.
  4. Substitute into the appropriate template and present as a clickable markdown link.

Troubleshooting

Problem Solution
"No data" / empty view Trace outside time window — widen startA/endA (±1h → ±1d → 90d).
404 ID wrong or not base64. Re-check org_id, space_id, project_id from the browser URL.
Span not highlighted span_id may belong to a different trace. Verify against exported span data.
org_id unknown ax CLI doesn't expose it. Ask user to copy from https://app.arize.com/organizations/{org_id}/spaces/{space_id}/….

Related Skills

  • arize-trace: Export spans to get trace_id, span_id, and start_time.

Examples

See references/EXAMPLES.md for a complete set of concrete URLs for every link type.

Source: SKILL.md on GitHub

Third-party checks

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides instructions for generating Arize UI links from trace and project identifiers. It contains no executable code or automated capabilities.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    1 finding · Score: 86/100

Provenance

Signed by skilld at 4e136f3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 19 hours ago.

Activeupdated 5 months ago

Capability

metadata
{
  "author": "arize",
  "version": "1.0"
}

Topics

  • arize
  • links
  • tracing
  • llm
  • monitoring
  • observability
  • datasets
  • evaluation

README badge

README badge for github/awesome-copilot/arize-link

What it does

Generates deep links to traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs in the Arize UI. Requires base64-encoded IDs and appropriate time-range parameters to avoid 404s and empty views.

Generated from the current SKILL.md.

Frequently asked

What IDs do I need to provide to generate a link?
You must provide org_id and space_id (both base64-encoded). Depending on the resource type, you also need project_id + trace_id for traces, session_id for sessions, dataset_id for datasets, queue_id for queues, or evaluator_id for evaluators. All path IDs must be base64-encoded or the link will 404.
How do I get the org_id and space_id?
Copy them directly from your Arize browser URL: https://app.arize.com/organizations/{org_id}/spaces/{space_id}/... The ax CLI does not expose org_id, so you must retrieve it from the UI.
Why is my trace link showing no data or empty results?
The time range parameters startA and endA are required and default to the last 7 days if omitted. If your trace falls outside that window, widen the time range by ±1 day or use a 90-day window as a fallback.
Do all IDs need to be base64-encoded?
Yes. All path IDs (org_id, space_id, project_id, trace_id, span_id, session_id, dataset_id, queue_id, evaluator_id) must be base64-encoded. If you provide a raw numeric ID, the URL will look valid but return a 404.
Can I link to a specific span within a trace?
Yes. Add the query parameter &selectedSpanId={span_id} to the trace URL to highlight a specific span, but verify the span_id belongs to that trace.

Generated from the current SKILL.md. These answers refresh after source changes.