The Sentry integration brings your organization’s error activity directly to your iPhone. New issues, regressions, and SLA alerts appear in your LogBrew feed the moment Sentry fires them, and resolving an issue in either app keeps both sides in sync automatically.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.
What you’ll see
- New issues: triggered when Sentry creates an issue for the first time
- Regressions: issues that were resolved but have re-occurred
- SLA breached: an issue has exceeded its SLA deadline (Critical)
- SLA high-risk: an issue is approaching its SLA deadline (Warning)
- Issue resolved: an issue resolved in Sentry is marked resolved in LogBrew
Connect Sentry
Authorize with OAuth
LogBrew opens the Sentry authorization screen. Sign in to your Sentry account if prompted, then approve the requested permissions for your organization.
Select projects to monitor
After authorization, choose which Sentry projects within your organization you want to monitor. Each selected project becomes a LogBrew project in your feed.
Sentry webhooks are registered at the organization level, not the project level. All Sentry projects you’ve added to LogBrew receive events through the same organization-level webhook. You can add or remove individual projects from the Projects tab at any time.
Severity mapping
| Sentry event | LogBrew severity |
|---|---|
| New issue | Critical |
| Regression | Critical |
| SLA breached | Critical |
| SLA high-risk | Warning |
| Issue resolved | Info |
Two-way resolve sync
Resolve sync works in both directions:- Resolve in LogBrew. Swipe to resolve on any Sentry event in your feed, and LogBrew resolves the corresponding issue in Sentry on your behalf.
- Resolve in Sentry. When a teammate resolves an issue in Sentry, LogBrew receives the webhook and marks it resolved in your feed automatically.
Staying connected
LogBrew refreshes your Sentry authorization automatically in the background. You don’t need to reconnect. The integration stays active for as long as you keep it.