Sentry Discover filters: limits of persisted queries across projects and sessions
0 reputation · 26 May 2025, 01:42 UTC
0 reputation · 26 May 2025, 01:42 UTC
I'm designing a team workflow around Sentry's Discover query builder and need to understand the boundaries of its filter persistence before committing to it. My goal is to share a standardized set of saved filters (by status, logger, and culprit) across an entire engineering team without each member rebuilding them manually.
From what I can tell, Discover filter selections survive page reloads and URL changes for an individual user, but the documented behavior is unclear on several edges: whether persistence is scoped per project or per organization, whether it applies to incognito or cleared-storage sessions, and whether saved queries propagate to teammates or remain strictly personal.
I'm also unsure how persistence interacts with the Projects dashboard, where tab order and keyboard navigation follow WCAG 2.1 AA, since some of our users navigate by keyboard alone and I want to confirm filter inputs are reachable and retain state in that flow.
Specifically: are Discover filter selections stored server-side per user, or only in local browser state? Can a saved Discover query be shared organization-wide, or must each user recreate it? Does filter persistence behave identically across projects within the same organization?
Discover filter selections that you apply but do not explicitly save are kept only in the browser’s URL and temporary localStorage. They disappear when you reload the page, change the URL manually, clear browser storage, or open an incognito/private window.
When you click Save in Discover, the query is stored server‑side under your Sentry user account. Saved queries appear in your personal “Saved Queries” list and are available from any browser or device after you log in.
The persistence mechanism relies on two layers: a client‑side layer for transient UI state and a server‑side layer for explicitly saved queries. Sharing a standardized set of filters across a team therefore requires each member to save the query individually (or use a shared Discover Dashboard, if your plan includes it).
If you need organization‑wide sharing without each user manually saving, confirm whether your Sentry plan includes Discover Dashboards (or another sharing feature). This detail changes the recommendation from “each user must save individually” to “you can publish a dashboard for the team”.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.