Reliability
Sentry
Error volume, crash-free sessions and checkout exceptions — the Reliability dimension.
At a glance
- Category
- Reliability
- Required
- Optional
- Auth
- OAuth preferred, API key or token as fallback
- Powers
- Technical
- Freshness
- Stale after 2 hours
- Webhook
- Yes — signed, per project
- Scopes
org:read project:read event:read
Connect it
- 1Press Connect on Sentry and use OAuth when it is available for your organization.
- 2Otherwise create an auth token at Sentry → Settings → Auth Tokens with org:read, project:read and event:read.
- 3Paste the token plus your organization slug and project slug.
- 4Seiton validates the token and then syncs from the Integrations page.
The auth token is created here: sentry.io.
Webhook
The exact URL — including this project's id — is shown in the product after you connect. Copy it from there rather than building it by hand.
https://www.seiton.online/api/webhooks/sentry?website_id={WEBSITE_ID}website_id is not optional
The signature is verified against the vault secret of that specific project. Without the query parameter the endpoint refuses the request rather than guessing which project a payload belongs to.
Worth knowing
- A webhook is optional. Cron sync alone is enough for the Reliability dimension.
- Crash-free sessions are omitted when Sentry has not reported them. An empty tile is honest; an invented 99.8% would not be.
- Zero errors is a valid reading and is shown as zero, not as missing data.
Disconnecting
Disconnect from the Integrations page. Seiton deletes the stored credentials, removes any webhook endpoint it created in your account, and strips the fields this provider owned out of your snapshots — those metrics go back to insufficient data rather than freezing at their last value.
Revoking the token or OAuth grant inside Sentry works just as well and stops reads immediately. The connection then shows as revoked on the next sync, with the reason.