Sentry integration

If your team already uses Sentry, its measurements can sit beside your own. Launchpad → Integrations → Sentry connects a Sentry organisation and pulls its projects into your install. Reading the page needs the Integrations capability, which is on by default.

Connecting

Connecting, changing and disconnecting is for administrators. You need a Sentry auth token with the scopes org:read, project:read and event:read. Add team:read and alerts:read if you want those too.

1. Paste the Token. Sentry user tokens start with sntryu_.
2. Optionally name the Organisation. Without it, the first organisation the token can see is used.
3. Save.

The region is found by itself. Your install asks sentry.io for the organisation and uses the region address Sentry gives, so EU and US organisations both work. The token is never shown again, only its last four characters.

What is pulled

Every five minutes, your install pulls:

• sessions by hour, status and environment;
• error events by hour, OS and environment;
• crash-free sessions and users, and user counts, over 24 hours, 7 days and 30 days;
• up to 25 releases per environment, with their health and adoption;
• 30-day breakdowns by platform, release, device and OS;
• the issues seen in the last 90 days;
• the users that events name, and each event in full.

The first pull reaches back 30 days. Later pulls re-read the last 48 hours. Pulled data is kept for 90 days. Pull now runs a pull immediately. Disconnect removes the pulled data, but keeps the applications it created.

The page

The Sentry page lists every project with its platform, environments, the events kept, and the application it became here. Environment chips filter it. Each project shows its sessions, crash-free rates, open issues, latest issues and releases.

Mobile projects become applications

A Sentry project whose platform is a mobile one becomes a mobile application here automatically, with a "via Sentry" badge. That covers React Native, iOS, Android, Flutter, Expo and Unity, among others. Its Overview shows:

• crash-free people and error-free sessions;
• open issues and releases with their health;
• the split by build, platform, OS version and handset.

Sentry keeps no single session. So for these applications, the person is where a story starts. A list of the people the events name shows their handset, OS, build, event count, and first and last seen. One person's events from the last 90 days are read from Sentry when you ask. One event shows the exception and its frames, the handset and app, and the breadcrumbs: the screens, taps, calls and log lines just before it.

Session replay, errors and API calls are hidden from the menu for these applications. Those come from Obscenter's own agents, which a Sentry project does not have. To get them as well, add the React Native agent to the app.

With the assistant

The AI assistant can read mobile crashes from the Sentry data, so you can ask which release started crashing.