Sentry integration
Error volume, day by day. Every other tool here watches what customers did; this one watches whether the product let them — and when a spike happens, somebody in engineering already knows why.
Sentry metrics Swoop can read
Read-only, and only what you point it at.
- Error events
- Errors dropped by quota
- Transactions traced
History arrives on connect. Sentry hands over past values, so signals can appear on the first sync.
Connecting it
A couple of minutes. An auth token from Sentry and your organisation slug — the one in sentry.io/organizations/<slug>/. Read scopes only.
- 01Auth token
Sentry: Settings → Account → API → Auth Tokens → Create New Token. Tick org:read and project:read; Swoop never writes.
- 02Organisation slug
The bit after /organizations/ in your Sentry URL. Paste the whole URL if it is easier.
- 03Regionoptional
us or eu — a token made in one region will not work on the other.
- 04Choose what it may watch
Every source states what it is allowed to look at. Ingesting everything available is how this becomes another dashboard nobody opens.
Credentials are encrypted and used read-only — nothing is ever written back to Sentry. Answers are synthesized by an open-weights model on Amazon Bedrock, so no foundation-model vendor sees your data; Enterprise runs that model in your own AWS account.
Include Sentry metrics in Swoop panels
Free to start, and you only pay for panels that answer.
Start free