Skip to content

Sentry integration

Connect DXDT to your Sentry organization for read-only error tracking, release, and issue insights. DXDT never modifies anything in Sentry — it only reads.
Setup time ~5 minutes
Difficulty Easy

Access required: Member role or above

Prerequisites

  • An active Sentry organization — either SaaS at sentry.io or a self-hosted Sentry instance.
  • Your organization slug, visible in any Sentry URL: sentry.io/organizations/<org-slug>/.
  • Permission to create an Auth Token on your Sentry account (Member and above).

Setup

1. Open the Auth Tokens page

Sign in to Sentry and go to Settings → Account → Auth Tokens (direct link: sentry.io/settings/account/api/auth-tokens/).

Note

For the quickest setup use a User Auth Token. If you'd rather not tie the connection to a person, create the token under a dedicated service user.

2. Create a read-only token

Click Create New Token and configure it as follows:

  • Name it something identifiable, e.g. DXDT (read-only).
  • Grant only these scopes: org:read, project:read, project:releases, event:read.
  • Do not grant any :write or :admin scopes — DXDT never needs them.

3. Copy the token value

Click Create Token and copy the generated value immediately.

Note

Sentry shows the token only once. If you lose it, revoke it and create a new one.

4. Note your base URL (self-hosted only)

If you run self-hosted Sentry, note your instance URL (e.g. https://sentry.acme.internal). SaaS users on sentry.io can leave the Base URL field blank.

Configuration fields

Field Where to find it
Auth Token (auth_token) The token you copied in Step 3.
Organization Slug (org_slug) The slug from your Sentry URL, e.g. acme-inc — the slug, not the display name.
Base URL (base_url) Leave blank for sentry.io SaaS. For self-hosted, enter your instance URL, e.g. https://sentry.acme.internal.

Verify the connection

Open the Configuration tab, paste the values, and click Install & Configure. Within a few seconds the Live Status panel on the Overview tab should show your organization name and a green connected indicator.

Security

Your token is stored encrypted and scoped to your tenant. DXDT uses it only for read-only Sentry operations.

Troubleshooting

401 Unauthorized or "invalid token"

The token is wrong, expired, or was revoked. Recreate the token in Sentry and confirm you pasted the full value with no leading or trailing spaces.

"Organization not found"

The organization slug is incorrect. Copy the slug exactly as it appears in your Sentry URL. It is lowercase and hyphenated, and is not the display name.

Self-hosted instance can't be reached

The Base URL is wrong or unreachable from DXDT's network. Confirm the Base URL includes https:// and no trailing path, and that the instance is reachable from the public internet or your peering.

Vendor documentation: https://docs.sentry.io/account/auth-tokens/