Skip to content
Probe Docs

Filter Folders

Filter Folders are saved filter shortcuts in the Sidebar. You build a filter once — say, “every 4xx response from api.staging.example.com” — give it a name, and the next time you need that view it’s a single click. They’re a productivity tool for recurring debugging tasks, not a capture filter.

Filter Folders only narrow what’s shown. They don’t drop traffic. To stop traffic from being captured in the first place, see Domain Watch.

Creating a filter folder

Section titled “Creating a filter folder”
  1. Set up the view you want — type a query into the FilterBar, pick a host in the sidebar, choose a status range, whatever combination matches the slice of traffic you care about.
  2. In the sidebar’s Filter Folders section, click + (or right-click the section header).
  3. Give the folder a name. Pick something obvious — 4xx errors, staging POSTs, auth flow.
  4. Confirm. The folder appears in the section.

Behind the scenes, the folder stores the FilterBar query plus any structural filters that were active when you saved it.

Using a filter folder

Section titled “Using a filter folder”

Click a folder to apply its filter. The log table immediately narrows to the matching subset. Click All at the top of the sidebar to clear the filter and show everything again.

Filter Folders compose with other filtering:

  • They combine with search in the FilterBar — click the folder, then type extra keywords to slice further.
  • They respect Domain Watch — a folder can never reveal traffic that was never captured.
  • They work in both Sequence and Structure view.

Useful filter folders

Section titled “Useful filter folders”

A few patterns worth saving once:

  • All 4xx — catch client-side errors at a glance during a QA pass.
  • All 5xx — server errors only; the on-call view.
  • Calls to api.staging.example.com — when you bounce between prod and staging traffic in the same session.
  • POST /login — focus on the auth handshake while debugging session state.
  • Image responses — Content-Type: image/* to audit asset loading.
  • Slow requests — combine with the duration sort in the log table to spot the slowest endpoints in your saved slice.

Folders are stored per machine, not per session. They follow you across tabs and across .pro files — so a folder you make today is still in your sidebar tomorrow, no matter which session you open.

Renaming and deleting

Section titled “Renaming and deleting”

Right-click a folder for the context menu:

  • Rename — edit the display name without touching the query.
  • Edit query — change what the folder filters by.
  • Delete — remove the folder. The query is gone; any captured traffic stays.

There’s no undo for delete, but recreating a folder is one click + typing a name, so this rarely matters.

How it differs from Domain Watch

Section titled “How it differs from Domain Watch”

The two features look similar — both reduce what you see — but they sit at different points in the pipeline:

FeatureWhen it actsReversible?
Domain WatchAt capture (drops requests before they hit the log)No — dropped traffic is gone
Filter FoldersAt display (hides captured rows)Yes — clear the filter, rows reappear

A practical workflow uses both: Domain Watch to keep the capture clean, Filter Folders to slice what got captured into views that match how you debug.

For domains you actively never want to see (telemetry, OS keepalives, your team’s metrics endpoint), use the Ignored list instead — right-click a domain and choose Ignore, or open the sidebar’s Ignored entry and click + to add one by name. Ignored hosts are dropped at capture, persist across app restarts, and don’t even produce a teaser. See Domain Watch → Ignored Hosts for the full picture.

Section titled “Related”