Exploring traces

Every run your Rius agents produce, from the list view down to a single span’s attributes.

Find the trace

Traces lists every trace in the workspace, newest first, refreshing automatically (the interval selector sits top right). Each row shows the root span’s name, trace ID, error count, span count, token total, computed cost, latency, and status. Search by name or trace ID, filter by status, and narrow the time range with the 1d / 7d / 30d / custom presets. The Spans tab is the same list at span granularity.

Trace status

Status is derived from the spans themselves rather than reported by your agent, and it has three values:

The third state goes by more than one name: the badge reads running…, the filter bar calls it incomplete, and the query API reports it as Incomplete. All three are the same thing, a span that has started and not ended.

A run only ever reads as running… when partial spans are enabled. Without them a span reaches the platform once, at the moment it ends, so a run is invisible while it is in flight and a crashed run never arrives at all. With them enabled you see the run while it is still going, and if the process dies mid-run the last state it reported stays behind as running… rather than disappearing. That makes the status a useful filter in its own right: a trace still showing running… long after the work should have finished is a crash, a hang, or a process that was killed before it could report.

Waterfall view

Open a trace to see its spans as a tree on a timeline. Spans are badged by kind (chain, llm, tool), LLM spans show their token counts inline, and failed spans are highlighted along the path from the root to the error. The header summarizes the whole trace: duration, span and error counts, total tokens, and cost. For an error span, the detail panel leads with the exception and traceback:

Map view

The Map tab lays the same trace out as a graph, one node per span, with selectable lenses for latency, cost, tokens, and errors. Use it when the tree gets deep and you want to see where the time or money went at a glance:

Inspect a span

Select any span to inspect it. LLM spans get a Model section computed from their OpenTelemetry GenAI attributes: provider, requested and response model, input and output tokens, and cost:

The Input / Output tab renders the prompt and completion when the span carries content attributes; see attribute interoperability for the message shape. Content capture is opt-in end to end: if the SDK’s privacy controls strip content, or your instrumentation never records it, the tab says so and the rest of the span (timings, tokens, cost) still works. Raw shows the span exactly as ingested.

Share what you found

Share on the trace list creates a public link to a frozen window of the current view, useful for handing a failure to a teammate without adding them to the workspace. Links are managed (and revoked) in Settings.

Next steps

• Monitoring usage and cost: the aggregate view of everything the traces show individually.
• Span attribute reference: the attributes behind the Model section and the Input / Output tab.