Docs / Observability and data

Sentry

Connect a Sentry account with read-only OAuth so the agent can investigate issues, stack traces and releases.

The Sentry connector gives the agent read-only access to your Sentry account. You authorize it with OAuth, so you never share a password or paste a token. The agent uses it to find errors, read stack traces and link a failure to a release.

Connect

As a team Administrator, open Connectors → Connect → Sentry.
Click Authorize Sentry. Sentry opens in your browser.
Approve the OAuth request for the Sentry account you want to use.
Your browser sends you back to the Pangea app, and the connection appears in Connectors.

Tip

If nothing happens after you approve, check that your browser allowed the popup and that your OS opens pangea:// links with the Pangea app.

The connector works with Sentry's hosted service at sentry.io.

What the grant covers

Pangea requests these read-only scopes:

org:read project:read team:read member:read event:read

The grant covers the whole Sentry account, not one organization. The agent picks the organization when it runs a query. If your account belongs to several organizations, name the one you mean.

The connection cannot resolve, assign or delete issues. Make those changes in Sentry.

What the agent can do for you

Select the Sentry connection in the conversation, then ask things like:

"What are the top unresolved errors in checkout since the last deploy?"
"Show me the stack trace and latest event for this issue."
"Which release introduced this error, and which commit is likely to blame?" The agent can combine Sentry with your GitHub connection to answer this.

To check access, ask for a short list of issues in the organization and project you expect.

Warning

Event payloads can contain private application data. Keep queries to the incident window, and think about who can read the conversation before you share results.

Permissions

Team Administrators connect and remove this connection. They can limit who uses it with a member allow-list. Sentry's own permissions for the authorizing user stay the outer limit.

Access errors and removal

After an access error, check the organization, the project permissions and which Sentry user authorized the app. Connecting the same Sentry user again replaces the stored credentials on the existing connection.

Removing the connection in Pangea does not delete Sentry events or results already in a conversation. To fully end access, also revoke the Pangea app in your Sentry account settings.

See Sentry API authentication for details on Sentry's OAuth.

Questions? augusto@pangea.buildPrivacy · Terms