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 into everything happening across your connected services. Events from Sentry, Vercel, Railway, PostHog, Linear, and Stripe all flow into a single chronological list, so you never have to switch between dashboards to understand the health of your projects.

​
Severity levels

Every event in LogBrew carries one of three severity levels, shown as a colored badge on each card:

Critical

Red badge. Errors, crashes, SLA breaches, payment failures, and failed deployments that need immediate attention.

Warning

Yellow badge. Elevated error rates, high-risk SLAs, canceled deployments, and other conditions worth monitoring.

Info

Blue badge. Successful deployments, issue SLA updates, and informational payment events.
Severity colors appear consistently across the app: in the feed, on the app icon badge, and in push notifications. They are the primary signal for how urgently you need to act.

​
Anatomy of an event card

Each card in the feed shows you the key details at a glance without tapping:
  • Severity badge: the colored indicator described above
  • Source icon: the provider logo (Sentry, Vercel, Railway, PostHog, Linear, or Stripe)
  • Title: the event name, such as “NullPointerException” or “Deployment failed”
  • Project name: which of your connected projects this event belongs to
  • Timestamp: how long ago the event arrived

​
Viewing event details

Tap any event card to open the detail view. Here you can see the full stack trace, environment metadata, and all context LogBrew received from the provider. The detail view also gives you these actions:
Mark the event as resolved. LogBrew syncs the resolution back to the provider, so resolving in LogBrew also resolves the issue in Sentry, Linear, or wherever the event originated. If a teammate resolves the same issue in the provider, LogBrew updates automatically.
Share the event’s title, stack trace, and metadata via the iOS share sheet. You can send it to Slack, Messages, email, or any other app. You can also generate a temporary shareable link with a configurable expiry.

​
Filtering the feed

Filter chips at the top of the Feed tab let you narrow down what you see without leaving the screen:
FilterWhat it shows
AllEvery event from all connected projects
CriticalOnly red-severity events
WarningsOnly yellow-severity events
By ServiceEvents from a specific provider (Sentry, Vercel, etc.)

​
Live updates

The feed connects to LogBrew’s live event stream over WebSocket. New events appear as they arrive. You do not need to pull to refresh, though pulling still works to force an immediate sync. When your connection drops and reconnects, LogBrew automatically fetches any events you may have missed.

​
Event grouping

When the same error fires repeatedly in a short window, LogBrew groups the occurrences into a single card rather than flooding your feed. The card shows a count, for example CrashX × 500, so you understand the scale of the problem at a glance. The count stays current as more occurrences arrive.

​
Unseen indicators

Events you have not yet viewed show a small dot on their card. The red badge on the LogBrew app icon shows the count of unresolved critical events by default. You can change the badge to show all unresolved events in Settings, Notifications.

​
Swipe actions

Swipe a card left to reveal quick actions without opening the detail view:
  • Resolve: marks the event resolved and syncs it to the provider
  • Mute: silences future notifications for this specific event
Muting an event stops push notifications for it but keeps it visible in the feed. Use mute for noisy low-priority events you want to track without being interrupted.