Docs · Errors
Sentry
Error spikes become evidence on the incident, with the release that caused them.
What it watches
Sentry feeds Errors — Runtime errors so incidents say what broke — as Runtime errors.
What Keelnest reads
Organization auth token · issue summaries, error frequency, affected users.
Most AI-built apps have no Sentry. The error capture snippet is the fallback.
Read-only, like every connection: Keelnest never refunds, charges, changes a price, edits a setting or an environment variable, merges on its own or runs a migration. The credential is checked with one read call before it is stored, encrypted at rest, and can be revoked at the provider at any time. Security says the whole of it.
How to connect
- Create the auth token. Sentry > Settings > Auth Tokens > Create. Scopes: org:read, project:read, event:read. Open Sentry.
- Paste it into Keelnest. In your workspace, open Integrations, find Sentry and press Connect. Keelnest makes one read call to confirm the credential works, stores it encrypted, and starts reading on the next five-minute tick.
- Link the apps. Under Manage, pick which applications this account watches. An app linked to a host is checked the moment that host reports a deploy; an app linked to a payment or AI account starts building its baseline from that hour.
Start watching
Create a workspace and connect Sentry from Integrations, or run the free check on any public URL first. All docs.