Cockpitify Docs Search the docs⌘K Product Sign in Try the live demo

Track release health with Sentry

Updated · Pro and up · Phone · Web

Connect Sentry to see crash-free sessions and users per release, new issues, version adoption and an alert when a release crashes too often.

Release health shows how far each version of your app has spread and how often it crashes. Adoption comes from your own usage analytics; crashes come from Sentry.

Open it

  • Phone: on the Product tab, tap Release health in the list further down. Home has a link to it too.
  • Web: in the sidebar, Product → Release health.

You can also reach the Sentry connection from App → Connections → Sentry.

Create a Sentry token

  1. In Sentry, open User settings → Personal tokens and create a token.
  2. Give it org:read, project:read and event:read.
  3. Copy it.

Connect

  1. On Release health, choose the Data region: US or EU.
  2. Enter the Organization slug: the name in your Sentry address, <slug>.sentry.io.
  3. Paste the User Auth Token and tap Get projects.
  4. Pick a project.

The token stays in this app's Supabase Vault. Sentry is read every hour.

What you see

  • Newest release, healthy or under your line, against the release before.
  • Crash-free rate · 14 days.
  • Releases (last 7 days) with crash-free sessions and users. Tap a release for its details: sessions by status, the daily crash-free rate, its adoption and the issues first seen in it.
  • Version adoption for 7, 30 or 90 days.
  • Error events · last 24 hours and New issues (last 24 hours), with Open in Sentry.

Version adoption needs appVersion in the usage SDK, and it must match the release name in Sentry. Adoption shows even before you connect Sentry.

Stability alerts

Set the Crash-free line between 90% and 99.99%. When a release with at least 50 sessions drops under it, you get one notification. Make sure the Stability notification category is on; see Notifications.

For a notification within seconds of a new error, set up Instant alerts; see Instant alerts from Sentry.

If connecting fails

  • Sentry didn't accept the token. Copy it again, and check it's a personal token.
  • The token lacks permission. Give it org:read, project:read and event:read.
  • Sentry has no such organization for this token. Check the slug and the region.
  • This token sees no projects in the organization. The token's user needs access to the project.

To disconnect, tap Disconnect Sentry. The token is deleted from the Vault; version adoption stays.

Was this page helpful?YesNo
Ask a question
Questions? Ask me.I’m Murat, the indie developer behind Cockpitify.

I read every message and reply by email, usually within a day.