Saved Views

Saved views let you bookmark any filter query under a name and restore it instantly. Use them to track recurring investigations, share common dashboards with your team, or build a library of filters you reach for regularly.

Creating a view

Add --views::create:<name> to any filter query and submit:

level:error context.gateway:stripe @last-24h --views::create:stripe-errors

The current filter (everything except the --views::create part) is saved under the name stripe-errors.

Loading a view

Two ways to load a saved view:

Command:

--views:stripe-errors

Shorthand with #:

#stripe-errors

Both expand the saved filter inline. You can combine them with additional filters:

#stripe-errors level:critical

Managing views

List all views:

--views

Delete a view:

--views:stripe-errors::delete

Plan limits

The number of saved views per project depends on your plan:

When the limit is reached, the API returns a 403 with code: QUOTA_EXCEEDED.

Notes

• View names are case-insensitive
• Views are scoped to the project — not shared across projects
• The saved filter is a raw query string; any future changes to filter syntax may require re-saving