Skip to main content
Table views save a table’s filters, search, sort, and column layout as a named preset you can reopen with one click. Views are stored per project, so any member of the project can pick the same preset from the dropdown.
Table views picker open above the traces table

The view picker on the traces table, with three saved views.

Each view is scoped to one table (Traces, Spans, Sessions, Evaluations, and the others), so saving a view on Traces never clutters the dropdown on Spans.

​
Save a view

Set up the table the way you want it. The picker shows an amber dot when the current state has drifted from any saved view; open it and the Unsaved changes section appears:
  • Save changes writes back to the active view.
  • Save as new view prompts for a name.
  • Discard changes reverts to the active view (or to Default view if none is loaded).
Unsaved changes section in the views dropdown

The Unsaved changes section appears when the table state has drifted from the active view.

​
Example: Most expensive traces

Sort the Traces table by Cost descending, hide the columns you don’t need (root output, tags, metadata, session/user id), and save it as High-cost traces. Anyone in the project opening the Traces tab can pick that view from the dropdown to land on the same focused table.
Traces table with the High-cost traces view applied

The Traces table with the High-cost traces view applied: sorted by cost desc, with low-signal columns hidden.

​
What’s next

Full text search

Search across span input, output, and attributes; saved into a view alongside your filters.

SQL Editor

When a view’s filters are not enough, drop into raw SQL across traces, spans, signals, and evals.