Views

You'll often want to create a view that shows data organized and visualized a certain way on the same underlying data. Views are saved table configurations that preserve filters, sorts, column order and column visibility. All table-based layouts, including logs, experiments, datasets and projects support configured views.

Default locked views

Some table layouts include default views for convenience. These views are locked and cannot be modified or deleted.

• All rows corresponds to all of the records in a given table. This is the default, unfiltered view.

On experiment and logs pages:

• Non-errors corresponds to all of the records in a given table that do not contain errors.
• Errors corresponds to all of the records in a given table that contain errors.

On experiment pages:

• Unreviewed hides items that have already been human-reviewed.

Creating and managing custom views

In the UI

To create a custom view, start by applying the filters, sorts, and columns that you would like to have visible in your view. Then, navigate to the Views dropdown and select Create view.

After entering a view, any changes you make to the filters, sorts, and columns will be auto-saved.

To rename, duplicate, delete, or set as default, use the ... menu next to the view name.

In code

Views can also be created and managed programmatically via the API.

Access

Views are accessible and configurable by any member of the organization.

Best practices

Use views when:

• You frequently reapply the same filters.
• You want to standardize what your team sees.
• You want to review only a subset of records.

Make sure to use clear, descriptive names so your team can quickly understand the purpose of each view. Some example views might be:

• "Logs with Factuality < 50%"
• "Unreviewed high-priority traces"
• "Failing test cases"
• "Tagged with 'Customer Support'"
• "Lisa's test cases"