Filters

Filters let you save a specific view of your logs — which levels to show, which buckets, which tags, what search text — and come back to it later.

Default filter

Every project starts with an All Logs filter. It shows everything, unfiltered. You can’t delete it.

Creating a filter

1. Open a project’s log viewer
2. Set up your filters (levels, buckets, tags, search)
3. Click the save icon or use the filter header to create a new saved filter
4. Give it a name

The filter config is saved and appears in the project’s filter tree in the sidebar.

What’s saved in a filter

A filter configuration stores:

Field	Description
levels	Which log levels to show (info, debug, warn, error)
messageSearch	Substring search in log messages
bucketIds	Which buckets to include
tags	Tag key → selected values mapping
timeRange	Preset (5m, 15m, 1h, 6h, 24h) or custom from/to

Folders

Filters can be organized into folders for complex projects. Create a folder, then create filters inside it. Folders can be nested.

Example structure:

my-api
├── All Logs
├── Errors Only
├── API
│   ├── Slow Requests
│   └── 5xx Responses
└── Auth
    ├── Login Failures
    └── Token Expiries

Unsaved changes

When you modify a saved filter’s settings, the changes are local until you explicitly save them. A visual indicator shows unsaved changes. You can either save the changes or discard them to revert to the saved state.

Duplicating

Duplicate an existing filter to create a variation. Useful when you want a similar filter with one parameter changed.