Filters
Filters stores reusable search presets. A preset can combine method, host, path, status, source, text, and an HTTPQL expression.
Saving a Filter
- Open Filters and create a named filter.
- Select it from the list.
- Fill in the fields you need; leave other fields empty.
- Click Save in the editor.
Saved filters are held in the local browser's storage, not in the project database. Use Export and Import to transfer them between installations.
Applying a Saved Filter
Select a saved filter and click Apply to Search. Ogma opens Search with its saved criteria. Review them and run the search.
Search also offers Pin for frequently used HTTPQL expressions. These pinned queries are separate from the structured presets on the Filters page.
Managing Filters
Open Filters from the left navigation to see all saved filters.
| Action | How |
|---|---|
| Rename | Select the filter, edit its name, and Save |
| Edit criteria | Select the filter, update the fields, and Save |
| Delete | Select the filter and use Delete |
| Transfer | Export presets as JSON, then Import on the other installation |
Filters vs. Scope
Filters and scope serve different purposes.
| Filters | Scope | |
|---|---|---|
| Purpose | Reusable search criteria | Declares which targets are in scope |
| Effect | Narrows displayed results | Depends on the capture/intercept mode and the tool's scope setting; activating scope alone does not block all out-of-scope forwarding |
| Stored as | Local named search presets | Workspace/project scope configuration |
| Applies to | Search; HTTPQL can also be entered directly in HTTP History | Scope-aware capture, interception, and testing tools |
A filter does not prevent Ogma from capturing traffic. It only changes what you see in the table.