Agent dashboards group executions by agent identity. For production agents, emit a stableDocumentation Index
Fetch the complete documentation index at: https://docs.inference.net/llms.txt
Use this file to discover all available pages before exploring further.
agent.id and a readable agent.name. Keep agent.id stable
across deploys, environments, and display-name changes; use agent.name as the
human-readable label.
If you only provide agent.name, Catalyst can still show observed agents, but
renames and duplicate names are harder to group. Prefer both fields whenever you
control the agent wrapper.
Manual Agent Wrapper
UseagentSpan() or agent_span() around the product-level agent run. Child
model and tool spans created inside the wrapper inherit the active agent
identity in supported Catalyst tracing integrations.
Choosing IDs
Use IDs that are stable, readable, and unique within a project:| Good | Avoid |
|---|---|
support-triage-agent | SupportAgent v2 |
refund-review-agent | random UUID per process |
billing-agent-prod | user-specific or request-specific values |
agent.role is optional. Use it when one workflow has multiple agents with
clear responsibilities, such as triage, refunds, or billing.
Existing OpenTelemetry Spans
If you author spans directly, setopeninference.span.kind = "AGENT" plus
agent.id, agent.name, and optional agent.role on the span attributes.
TypeScript
What Catalyst Uses
Catalyst readsagent.id first and falls back to agent.name when no stable ID
is present. The raw attributes remain on the span, and ingestion promotes them
into dashboard fields used by the Agents page.