NeMo Studio Traces

View as Markdown

Use Observability > Traces in the NeMo Studio workspace sidebar to inspect telemetry ingested from agent runs.

Traces is enabled by default. An administrator can disable it by setting studio.feature_flags.intake_enabled: false in the platform configuration and restarting Studio.

Traces and Spans Tables

The Traces and Spans tabs list ingested telemetry at different granularity:

TabColumns
TracesTrace, input, output, duration, span count, errors, tokens, cost, started.
SpansStatus, kind, span, input, output, subject, trace, duration, tokens, cost, started.

Select a row in either table to open the session it belongs to.

Session Detail

The session detail page shows a summary header, then the selected trace’s spans. Use the Tree / List toggle to switch between a nested span tree and a flat list, and Collapse all / Expand all to manage the tree view.

Selecting a span opens its detail body. Studio renders a specialized view for known span kinds — LLM, tool, agent, chain, embedding, reranker, retriever, guardrail, and evaluator — and falls back to a generic view for unrecognized kinds. Each span body includes metadata, an annotations panel, and a raw JSON view for debugging.

Evaluation test-case runs reuse this same session detail view; see Compare Runs Side by Side in NeMo Studio Experiments.