Browse a project's traces

Filter a project-scoped trace table, open the resizable trace detail sheet, and inspect spans, overview metrics, and metadata.

Open Project > Traces when you already know which application owns the behavior. This page is a project-scoped flat table. Selecting a row opens a resizable detail sheet while the table remains visible behind it.

Project Traces is not the three-pane Explorer. Use organization Explorer when you need a directory tree, a result list, and a detail pane in one workspace.

What the page shows

The route is /app/{organizationSlug}/projects/{projectId}/traces. The project in the route is applied to every trace query, so the filter sidebar does not show a redundant Project filter. Filter the table, select a row, then inspect the trace without leaving the result set.

Find a trace

Start with the date range, then combine the controls that separate the traffic you need.

Control	What it changes
Search	Matches trace name, trace ID, project, environment, status message, user ID, session ID, request IDs, attributes, tags, and custom attributes.
Environment	Narrows the project to a reported environment such as production, staging, development, test, or another emitted value.
Status	Finds `ok`, `error`, or `timeout` traces.
User ID	Follows traffic recorded for one user identifier.
Session ID	Collects traces recorded for one conversation or session.
Service name	Separates services or SDK emitters inside the project.
Date range	Limits the start-time window before pagination is applied.
Columns	Chooses which trace fields remain visible in the table.
Refresh	Reloads the current query without clearing its scope.

Filters combine. Search and date state are represented in the URL, so review the URL before sharing a filtered investigation. If a known trace is missing, widen or clear the date range first.

Inspect the detail sheet

Select a row to open a non-modal sheet from the right. Drag its left edge to change the width. The selected width is remembered for the trace detail sheet.

The sheet has three tabs:

Spans shows the trace or span execution tree. Select the root for trace details or select a child operation for span details.
Overview summarizes the trace duration, status, span count, errors, and timing shape.
Metadata shows recorded service, SDK, tags, identifiers, and custom trace attributes.

Inside Spans, the sheet separates the execution flow from the selected trace or span detail. This internal split is not a page-level third pane. The exact fields shown depend on what the integration captured. Model messages, tool inputs and outputs, audio, images, tokens, costs, events, and voice timings appear only when supported data is present and the viewer has access.

A repeatable investigation

Choose a date range that covers the event or deployment.

Filter by environment, status, service, user, or session before adding free text.

Select a trace and confirm its top-level status, duration, and span count in Overview.

Open Spans, follow parent-child order from the root, and select the first unexpected operation.

Inspect normalized attributes first, then raw recorded data only when you need the exact payload.

Check Metadata for service_version, SDK information, tags, and custom dimensions before comparing another trace.

Move from evidence to evaluation

Use Explorer to compare organization scopes or inspect dataset items. Use an ETL job to transform representative traces into versioned dataset items, then open Runs to review mapped conversations and their evaluation results.