Skip to content

Saved searches

Save a query you'll come back to — an error triage view, a service's traffic, a known-bad pattern — and reload it in one click.

From the search page, click Save. A saved search captures the query (and its index scope) under a name you choose. It belongs to the environment you saved it in.

When saving you choose its visibility:

  • Shared (the default) — visible to everyone; any user can load and run it. Other users run it read-only; they don't change your original.
  • Private — visible only to you.

Using saved searches

  • The saved-searches menu on the search page lets you reload one quickly.
  • The Saved page lists them with a filter box, each one's owner and visibility, and a pre-fetched result count so you can see at a glance which are firing. From there you can load, edit (rename / change visibility), or delete a search.

A saved search stores the query, not a frozen result set — reloading it re-runs the query against current data and your selected time range.

Scope and ownership

  • Saved searches are per-environment — switching environments shows that environment's saved searches.
  • You can edit and delete your own searches. Admins can use a "view all" toggle to see (and manage) every user's saved searches.

From saved search to dashboard or alert

A useful saved search is often the seed for more: drop it on a dashboard as a widget, or turn its query into a monitor that alerts when results cross a threshold.