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.

The Feed tab is your central view for everything happening across your connected projects. Events stream in live over a persistent WebSocket connection. New items appear at the top of the list as they arrive, with no manual refresh needed. Alongside the event feed, the Logs tab streams raw deployment and build output line-by-line while a deployment is active, so you can watch a build succeed or fail in real time.

​
How the live feed works

LogBrew keeps an open connection to the server while the app is in the foreground. Every event ingested from Sentry, Vercel, Railway, PostHog, Linear, or Stripe is pushed to your feed immediately. You will see a severity badge (red for critical, yellow for warning, blue for info), the source service icon, the event title, the project name, and the timestamp on each row.

​
Reconnection and gap recovery

Network interruptions happen. LogBrew handles them automatically. If your connection drops, the app retries in the background with up to 15 attempts, using jitter so retries do not all fire at the same instant. You do not need to take any action. The connection restores on its own once your network recovers. When you reopen the app after being offline, LogBrew runs a gap fetch: it requests any events that were received by the server while you were disconnected and prepends them to your feed. You will never come back to a stale feed missing events from while you were away. The same gap recovery runs after every reconnection, so even a brief network blip will not leave holes in your history.
The Logs tab also runs gap recovery on reconnect. If a deployment was in progress while you were offline, the logs you missed are fetched and prepended so you see the full build output.

​
Filtering the feed

You can narrow the feed by severity or by service at any time.
1

Open the filter controls

Tap the filter icon in the top-right corner of the Feed tab to reveal the filter sheet.
2

Choose a severity level

Select All, Critical, Warning, or Info. The feed updates immediately.
3

Filter by service

Tap By Service and choose one or more providers: Sentry, Vercel, Railway, PostHog, Linear, or Stripe. Events from unselected services are hidden.
4

Combine filters

Severity and service filters stack. For example, you can show only Critical events from Sentry.
To save a filter combination so you can return to it later, see Saved filters.

​
App icon badge

The badge on the LogBrew app icon shows the count of unseen critical events by default. You can change this to show all unresolved events in Settings, Notifications, Badge count.
By default the badge counts every critical event that arrived since you last opened the app. If you have multiple projects connected, critical events from all of them contribute to the total. Switch the badge mode to Critical only in Settings if you want it scoped more tightly, or mark events as resolved to bring the count down.
If the feed appears frozen, check your network connection. LogBrew retries automatically, but if all 15 reconnection attempts are exhausted (for example, a long airplane mode session), pull to refresh to manually re-establish the connection.
LogBrew fetches missed events every time the app comes to the foreground and re-establishes its connection. If a specific event is missing, check that the relevant project is still connected in Settings, Integrations.