Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt

Use this file to discover all available pages before exploring further.

Saved filters let you build named views of your event feed that you can switch to instantly. Instead of re-selecting severity, service, and project settings every time you open the app, you save the combination once and recall it with a single tap. A filter called “Critical Sentry errors from my-api” gets you straight to the events that matter, without any re-configuration.

​
What a filter can include

Every saved filter is a combination of up to four criteria. You can use any subset. A filter with only a severity level is as valid as one that combines all four.
CriterionOptions
SeverityAll, Critical, Warning, Info
ServiceSentry, Vercel, Railway, PostHog, Linear, Stripe
ProjectAny specific project you have connected
Search queryAny keyword or phrase to match against event titles and messages

​
Creating a saved filter

1

Set your filters in the Feed

Open the Feed tab and apply the combination of severity, service, project, and search query that you want to save.
2

Tap Save Filter

Tap the Save Filter option in the filter sheet. It appears once you have at least one filter criterion active.
3

Name your filter

Enter a descriptive name. Something like “Critical Railway crashes” or “Linear SLA breaches” works well. Tap Save.
The filter is immediately available in your filter list and persists across app restarts.

​
Applying a saved filter

  1. Open the Feed tab.
  2. Tap the Filter button.
  3. Scroll to the Saved Filters section and tap the filter you want to apply.
The feed switches to that filter instantly. To return to the default view, tap Clear or select All in the filter sheet.

​
Deleting a saved filter

You can delete a saved filter two ways:
  • Long-press the filter name in the filter list, then tap Delete.
  • Go to Settings, Saved Filters, swipe left on the filter you want to remove, and tap Delete.
Deleting a saved filter is permanent. The filter definition is removed but no events are deleted. You can recreate the same filter at any time.

​
Practical examples

Create a filter scoped to a specific project with severity set to Critical. Switch to this filter at the start of your on-call shift so your feed shows only the alerts you are responsible for.
If you are actively working on one service, save a filter for that project with severity set to All. You see everything from that project: errors, deployments, and warnings, without events from other services cluttering the view.
Connect Stripe and save a filter with the Stripe service selected and severity set to Critical. Drop into this view when you want a quick check on payment failures without digging through deployment noise.
Save a filter for the Linear service with severity set to Critical or Warning. SLA breach and high-risk events from Linear surface immediately when you switch to this view.
Saved filters are a great complement to push notifications. Set up notifications for critical events across all projects, then use saved filters to drill into a specific service or project when you want to investigate further.