// Sentry integration
Turn error volume into incident context instead of another noisy feed.
Beaam connects with a read-only auth token, discovers your Sentry projects, and reads each project's error rate every minute via the Stats v2 API. It alerts on a genuine spike — the K-of-N engine ignores one-off blips so only a real surge needs your attention.
Curated deliberately: a short list worth your attention, not every metric that exists. Each one needs repeated evidence before Beaam calls it — a single bad reading is not an incident.
| Signal | When Beaam speaks up |
|---|---|
| Error rate | More than 10 errors in 5 minutes → broken. |
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
setup
Connect a read-only Sentry token and choose the projects worth watching.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
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.
1 signals can raise an incident: Error rate. Everything else is collected for context but stays quiet until you opt in.
Connect a read-only Sentry token and choose the projects worth watching. Most connections are watching within a few minutes, and you can send a test alert immediately to prove the path works end to end.
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.
The free plan covers two integrations and five watched services, with email, push, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations and services, adding SMS — there is no per-host, per-check or per-alert metering.
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.