Saved Views

Saved views are named filter queries stored per-project. A saved view is a single string in the same query syntax as the filter bar.

Save one — from Logs

1. In the Logs view (1), type a filter into the search bar (/) and apply it.
2. Press s.
3. Type a name (the wizard suggests nothing — pick something memorable like “prod errors” or “slow payments”).
4. enter — the view is created.

The current filter is saved verbatim. Description is empty; you can edit it on the web if you want a longer explanation.

Browse and apply — Saved Views (3)

When you press enter, the TUI navigates back to the Logs view with the saved query both in the filter bar and applied to the log list. Same as if you’d typed it yourself and pressed enter in the search bar.

Quick recall — v from Logs

In the Logs view, v is a shortcut for “go to Saved Views”. Useful when you forget which filters you have set up.

Backend sync

The TUI hits /api/projects/[id]/saved-views for list/create/delete. The web console reads from the same table. There’s no caching — what you see in the TUI is what the backend has right now.

Common patterns

A few saved views worth setting up on day one:

• errors-1h — level:error,critical @last-1h
• slow-requests — context.responseMs:>500
• staging-only — context.env:staging
• today — @from:today
• my-service — context.service:<your-service-name>

Combine and re-save as you find recurring views.