Connect Sentry to ShipVitals
Crash-free rates, sessions and issues per project
AvailableRead-only key · about 3 minutes
What it reads
- org:read
- Finds the organisation and its region
- project:read
- Lists projects
- event:read
- Reads sessions and issues
Read-only: ShipVitals can't change anything at Sentry.
What ShipVitals keeps: The internal integration token, encrypted.
How to connect
- Open Settings → Developer settings → Custom integrations in Sentry.
- Create an internal integration named ShipVitals.
- Give it the read permissions listed below, save it, and copy its token.
- Enter your organization slug below.
About 3 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Health.
Figures it fills
- Sessions
- crash_free.sessions
- crash_free.users
- issues.new
- issues.unresolved
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- Sentry no longer accepts what ShipVitals signs in with. Create a new key, or connect again, and replace it in the connection.
- A permission is missing
- What ShipVitals has can't read everything it needs. Add the permissions under What it reads, or create a new key with them, and test again.
- Access removed
- ShipVitals' access was removed in Sentry. Connect it again; the history it brought in is kept.
- Rate-limited
- Sentry asked ShipVitals to slow down. Nothing to do: the sync carries on by itself and catches up.
- Quota reached
- The account used up a Sentry quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from Sentry: renamed, moved or removed. Review the connection's resources, or connect again.
- Sentry is unavailable
- Sentry is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach Sentry
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Sentry is reachable.
- An answer ShipVitals didn't expect
- Sentry answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- A field in the connection doesn't work with Sentry. Check it against How to connect, and test again.