Linking Sentry as a source
The Sentry connector can link data from your Sentry organization into PostHog.
Creating a Sentry Auth Token
Sentry supports several authentication methods, but for PostHog you should use an Auth Token.
- In Sentry, create a token from your account settings (for internal integrations or personal tokens).
- Give the token read access for the resources you want to sync.
- Copy the token and paste it into PostHog when linking your source.
For token setup details, see Sentry's Authentication docs.
Once the syncs are complete, you can start using Sentry data in PostHog.
To link Sentry:
- Go to the Data pipeline sources page in PostHog.
- Click + New source and then click Link next to Sentry.
- In Sentry, create an Auth Token and copy it. PostHog currently supports Auth Tokens only.
- In PostHog, enter your Sentry Organization slug and Auth Token.
- Click Next, choose the tables you want to sync, and then click Import.
Configuration
| Option | Type | Required |
|---|---|---|
Auth token | password | Yes |
Organization slug | text | Yes |
API base URL | select | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | A Sentry project that error and performance events are reported to. | Full refresh | — | — |
teams | A team within the Sentry organization that owns projects. | Full refresh | — | — |
members | A member of the Sentry organization. | Full refresh | — | — |
releases | A release tracked in Sentry, used to associate errors with deployed code versions. | Full refresh | — | — |
environments | An environment (e.g. production, staging) that events are tagged with. | Full refresh | — | — |
monitors | A cron monitor that tracks the health of scheduled jobs. | Full refresh | — | — |
issues | A group of similar error events aggregated into a single issue. | Incremental, Full refresh | lastSeen, firstSeen | — |
project_events | Individual error events captured for a project. | Incremental, Full refresh | dateCreated | — |
project_users | Users seen in events for a project. | Full refresh | — | — |
project_client_keys | Client (DSN) keys that authenticate event submission to a project. | Full refresh | — | — |
project_service_hooks | Service hooks that send a project's events to external services. | Full refresh | — | — |
issue_events | Individual error events belonging to a specific issue. | Incremental, Full refresh | dateCreated | — |
issue_hashes | Grouping hashes that determine which events are bucketed into an issue. | Full refresh | — | — |
issue_tag_values | The distinct values of a tag observed across an issue's events, with counts. | Incremental, Full refresh | lastSeen | — |
Available datasets and endpoints
The Sentry source currently supports syncing the following datasets and API endpoints:
| Dataset | Endpoint path |
|---|---|
projects | /organizations/{organization_slug}/projects/ |
teams | /organizations/{organization_slug}/teams/ |
members | /organizations/{organization_slug}/members/ |
releases | /organizations/{organization_slug}/releases/ |
environments | /organizations/{organization_slug}/environments/ |
monitors | /organizations/{organization_slug}/monitors/ |
issues | /organizations/{organization_slug}/issues/ |
project_events | /projects/{organization_slug}/{project_slug}/events/ |
project_users | /projects/{organization_slug}/{project_slug}/users/ |
project_client_keys | /projects/{organization_slug}/{project_slug}/keys/ |
project_service_hooks | /projects/{organization_slug}/{project_slug}/hooks/ |
issue_events | /issues/{issue_id}/events/ |
issue_hashes | /issues/{issue_id}/hashes/ |
issue_tag_values | /issues/{issue_id}/tags/{key}/values/ |