Skip to main content
Connecting Sentry lets Traversal pull error context and issue information so it can reference ongoing and past incidents during investigations.

​
What Traversal reads

  • Events — error and performance events
  • Issues — grouped errors with status and metadata
  • Releases — release metadata used to correlate errors with deploys
Traversal only ever reads from Sentry — every scope below is read-only.

​
Required scopes

Grant the following read-only scopes. If your Sentry instance offers Read / Write / Admin access per resource, set everything to Read.
Use the API auth token, not a DSN — the DSN is the write-only SDK ingestion key and will not authorize reads.

​
Setup

An internal integration is org-scoped, least-privilege, and survives people leaving the team.
1

Create an internal integration

  1. In Sentry, go to Settings → Custom Integrations → Create New Integration → Internal
  2. Give it a name (e.g. traversal-prod)
  3. Grant read access on the scopes listed above
  4. Copy the generated auth token
2

Configure in Traversal

Go to Company Knowledge → Integrations, select Sentry, and enter:
  • Auth Token — the internal-integration token you just created
  • Organization Slug — the org segment in your Sentry URLs (e.g. my-org in sentry.io/organizations/my-org)
  • Base URL (optional) — leave blank for sentry.io. Set https://de.sentry.io for the EU region, or your instance URL for single-tenant / self-hosted Sentry
Click Save.

​
Private network access

If the service endpoint is not directly reachable by Traversal (as is common with self-hosted services), deploy a Traversal Connector in a network that can reach it. When configuring the integration, select that connector under Network Access Needed. The service endpoint does not need public internet exposure. See Set up the Traversal Connector for deployment and network requirements.

​
More information