Monitor Sentry.Hear only when it matters.
Turn error volume into incident context instead of another noisy feed.
What Beaam does with Sentry
Beaam connects with a read-only auth token, discovers each project/environment pair, and checks its error count and affected users over the latest 5 minutes. It also reads project-wide accepted and dropped ingestion outcomes. Alerts describe the fixed rule Beaam actually evaluates; they do not claim to detect a statistical spike.
What raises an incident
Curated deliberately: a short list worth your attention, not every metric that exists. Signals that can blip need repeated evidence before Beaam calls them; a reading that is definitive by nature — the provider reporting a failure outright — alerts on the first observation.
| Signal | When Beaam speaks up |
|---|---|
| Error volume | More than 10 errors in 5 minutes on 2 of 3 checks → broken. |
| Rate-limited events | Any error event dropped by Sentry rate limits in the last hour → broken. |
| Invalid events | Invalid error events on 2 of 3 checks → degraded. |
| Incident signals | New/regressed high-severity issues and failed Sentry monitors → broken when the project exposes them. |
| Trace failures | At least 10 spans with a 10% failure rate on 2 of 3 checks → degraded, tracing projects only. |
Also collected, but quiet
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
- Errors and affected users
- Accepted and dropped events
- Release health and performance
What connecting needs
- Sign in with Sentry:
org:read,project:readandevent:read. - Auth token instead:
project:readandorg:read; addevent:readto get new and regressed issue alerts. - Self-hosted Sentry: token only, and the instance must be reachable from the public internet.
What Beaam will not tell you
Stated rather than discovered later. Some of these are deliberate — an alert that is not about your system is noise — and some are simply where this integration's view ends.
- Thresholds are fixed rules, not spike detection, and count the error event category only.
- Crash-free rate alerts need at least 50 sessions in the hour; span-failure alerts need at least 10 spans.
- Sentry's ingestion outcomes cannot be filtered by environment, so dropped-event counts cover the whole project.
- A project with no environment cannot be monitored.
setup
Designed to stay small
Sign in with Sentry and approve read-only access — no token to create. Then choose the projects worth watching; a read-scoped auth token still works instead.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Never writes, and revocable
Beaam never writes to Sentry. Credentials are encrypted with AES-256-GCM using a key held as a deploy secret, and are deleted immediately when you disconnect.
Questions
What does Beaam alert on for Sentry?
5 signals can raise an incident: Error volume, Rate-limited events, Invalid events, Incident signals, Trace failures. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect Sentry?
Sign in with Sentry and approve read-only access — no token to create. Then choose the projects worth watching; a read-scoped auth token still works instead. Most connections are watching within a few minutes, and you can send a test alert immediately to prove the path works end to end.
Does Beaam need write access to Sentry?
No. Beaam only ever performs read operations — there is no code path that writes to a connected provider. Worth separating from that: what Beaam *does* and what a token *permits* are different things. Where Sentry offers a read-scoped credential, use it; some providers only issue tokens carrying broader rights than Beaam uses, which is a property of their API rather than of Beaam's behaviour. Scope it as narrowly as the provider allows. Credentials are encrypted with AES-256-GCM before storage and deleted the moment you disconnect.
What does Sentry monitoring cost?
The free plan covers two integrations and five watched services, with email, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations, services and organizations, with collaborators included — there is no per-host, per-check or per-alert metering.
Watching more than Sentry?
Most stacks are several services with seams between them, and the seams are where the damaging failures hide. Beaam correlates across every connected integration, so a database problem reads as one incident rather than five alarms from five tools.