Skip to main content

Sentry

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable PyAirbyte
Connector type
Available Data replicationAvailable Agent(learn more)
Support Level
Airbyte
Connector Version
1.1.1 (last updated 3 days ago)
Sync Success Rate
High
Usage Rate
High
Data workers used
0.2 per sync (Learn more)
Definition ID
cdaf146a-9b75-49fd-9dd2-9d64a0bb4781

This page contains the setup guide and reference information for the Sentry source connector.

Prerequisites​

To set up the Sentry source connector, you need:

For Sentry SaaS, you can create an organization-wide token with a Sentry internal integration. Configure the integration with read access for organizations, projects, and issues and events to sync every stream.

Set up the Sentry connector in Airbyte​

  1. In Airbyte, select Sources, then select New source.
  2. Select Sentry.
  3. For Authentication Tokens, enter your Sentry authentication token.
  4. For Host Name, keep sentry.io for Sentry SaaS, or enter the hostname of your self-hosted Sentry server without https:// or a path. You can also use your Sentry SaaS region-specific domain, such as us.sentry.io, us2.sentry.io, or de.sentry.io.
  5. For Organization, enter the organization slug. Use the slug from your Sentry URL, such as my-org in https://my-org.sentry.io, not the display name.
  6. For Projects, enter one or more project slugs. The events, issues, and project_detail streams sync each project you list. Organization-level streams aren't limited to these projects. Setup only checks the first project, so a misspelled slug later in the list shows up as an error on the first sync.
  7. Optionally, for Events start date, enter the earliest date to sync events from, in UTC, such as 2026-01-01T00:00:00Z. Only the first sync of the events stream uses it, and later syncs continue from where the previous sync stopped. Other streams always sync their full history. Leave it empty to sync every event Sentry still has.
  8. Optionally, turn off Events full payload to sync summary events without stack traces. When it's on, Sentry returns at most 10 events per page.
  9. Optionally, for Number of concurrent workers, enter a value from 1 through 20. The default is 5. With several projects, this also sets how many projects are read at once.
  10. Leave Discover Event Fields empty. None of the connector's streams read this setting.
  11. Select Set up source.

Supported sync modes​

The Sentry source connector supports these sync modes:

Supported streams​

StreamData syncedSupported sync modesCursor field
EventsError events for each configured projectFull refresh, incrementaldateCreated
IssuesIssues for each configured projectFull refresh, incrementallastSeen
ProjectsProjects in the configured organizationFull refresh, incrementaldateCreated
Project DetailFull details for each configured projectFull refresh—
All Projects DetailFull details for every project in the configured organizationFull refresh—
ReleasesReleases in the configured organizationFull refresh, incrementaldateCreated

The all_projects_detail stream makes one project-detail request for every project returned by the organization-level list endpoint.

Incremental sync behavior​

The streams differ in how much filtering Sentry does for you, which changes what an incremental sync returns:

  • events passes the cursor value to Sentry in the start query parameter, so Sentry returns only events created after the previous sync. Unless Events full payload is off, the stream also requests full event bodies, including stack traces, so records are large compared to the other streams.
  • With several projects, events and issues keep a separate cursor for each project. A project you add to an existing connection doesn't start from the beginning: its first sync starts from the most recent cursor of the projects already synced, so its older events and issues are skipped. To sync its history, refresh the events and issues streams after you add it, which re-reads every project in those streams, or sync the new project in its own connection.
  • issues filters server-side with a lastSeen:>{cursor} search query. An issue is synced again every time Sentry sees it again, so a long-lived issue produces a new record in many syncs.
  • projects and releases use dateCreated, and neither endpoint accepts a date filter. The connector reads the list and drops records created before the previous sync's cursor value. Because the cursor is a creation timestamp, later changes to a project or release, such as a status change or a new deploy, don't generate a new record. Sync these streams in full refresh mode if you need their current values.
Version 1.0.0

The projects stream now returns only projects in the configured organization. The avatar, color, isInternal, isPublic, organization, and status fields return null in this stream. Sync all_projects_detail to retrieve these fields for every project. For upgrade instructions, see the Sentry migration guide.

Authentication token scopes​

The authentication token must include the scopes required by the streams you sync. To sync every stream, grant org:read, event:read, and project:read.

StreamEndpointRequired scope
EventsGET /api/0/projects/{organization}/{project}/events/project:read
IssuesGET /api/0/projects/{organization}/{project}/issues/event:read
ProjectsGET /api/0/organizations/{organization}/projects/org:read
Project DetailGET /api/0/projects/{organization}/{project}/project:read
All Projects DetailGET /api/0/projects/{organization}/{project}/ (per org project)org:read, project:read
ReleasesGET /api/0/organizations/{organization}/releases/project:read

If the token is missing a scope, the corresponding stream returns an HTTP 403 error. See the Sentry permissions and scopes reference for details.

Airbyte tests the connection by reading the details of the first project in Projects, so setup fails without project:read on that project, even if you plan to sync only organization-level streams.

Limitations and troubleshooting​

Event retention​

warning

Sentry SaaS retains error events for 30 or 90 days, depending on your plan. If you use Full Refresh - Overwrite, a sync replaces older destination records with only the events still available from Sentry. Use an append mode if you need to keep events beyond Sentry's data retention period.

Rate limits​

Sentry applies request and concurrency limits per caller and endpoint. The limits are returned in the X-Sentry-Rate-Limit-* response headers and can vary by endpoint. If syncs receive HTTP 429 responses, reduce Number of concurrent workers. See Sentry's rate limit documentation.

Deprecated endpoints​

Sentry marks the project-scoped issues endpoint that the issues stream uses as deprecated, and recommends the organization-level issues endpoint instead. The endpoint still returns data, and Sentry's API deprecation policy requires advance notice before removal. Version 1.0.0 made the equivalent switch for the projects stream after Sentry deprecated the legacy projects endpoint.

Organization or project not found​

If setup or a sync fails with the error Sentry organization or project is missing or invalid. Check the organization and every slug in Projects., Sentry returned HTTP 404 for a request. A failed sync also lists the request that failed, which shows the organization and project slug Sentry didn't find. Check the following:

  • Organization and Projects contain slugs, not display names. Slugs are lowercase and use hyphens instead of spaces.
  • Each project belongs to the configured organization.
  • Host Name matches the region or self-hosted server where the organization lives. For example, an organization on de.sentry.io returns 404 when you query us.sentry.io.
  • The token was issued for that organization. An internal integration token only works for the organization that owns the integration.

Airbyte rejects empty or whitespace-only values for Organization and Projects before contacting Sentry.

Pinning a connection to version 1.0.16 or earlier​

In version 1.1.0, the Project setting became Projects, a list. The connector converts an existing single slug to a one-item list the first time version 1.1.0 runs, and Airbyte saves the converted setting. Existing connections keep their events and issues cursors and don't need any action.

If you pin a connection back to version 1.0.16 or earlier after that conversion, the connection fails until you edit Projects back to a single slug. Earlier versions can't read the per-project cursors that 1.1.0 saves, so the first sync after the rollback re-reads the events and issues streams in full.

IP allow list​

If you use Airbyte Cloud and your organization restricts access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Reference​

Config fields reference

Field
Type
Property name
string
auth_token
string
organization
array<string>
project
array
discover_fields
boolean
events_full_payload
string
hostname
integer
num_workers
string
start_date

Changelog​

Expand to review
VersionDatePull RequestSubject
1.1.12026-11-0390736Update dependencies
1.1.02026-10-3089563Sync multiple projects (existing single-project settings are migrated automatically), and add the Events start date (start_date) and Events full payload (events_full_payload) options
1.0.162026-10-2089398Update dependencies
1.0.152026-10-1388408Type the sentry:replay_rage_click_issues project option as boolean in project_detail and all_projects_detail
1.0.142026-10-1388806Update dependencies
1.0.132026-10-0688017Update dependencies
1.0.122026-09-2987328Update dependencies
1.0.112026-09-2286799Update dependencies
1.0.102026-09-1678108Improve Sentry configuration validation and 404 error messaging.
1.0.92026-09-1586225Update dependencies
1.0.82026-09-0885631Update dependencies
1.0.72026-08-1884735Update dependencies
1.0.62026-08-1184114Update dependencies
1.0.52026-08-0483604Update dependencies
1.0.42026-07-2883101Update dependencies
1.0.32026-07-2182603Update dependencies
1.0.22026-07-1482008Update dependencies
1.0.12026-07-1381707Scope the 1.0.0 breaking change to the projects stream and emphasize the risk of data loss in the migration guide
1.0.02026-07-1380190Breaking: migrate the projects stream to the org-scoped endpoint (Sentry deprecated the legacy /projects/ endpoint). The stream now returns only projects belonging to the configured organization, and no longer returns avatar, color, isInternal, isPublic, organization, status. Added the all_projects_detail stream, which returns full project details (including those six fields) for every project in the organization. See the migration guide.
0.9.272026-06-3081219Update dependencies
0.9.262026-06-2380622Update dependencies
0.9.252026-06-1680036Update dependencies
0.9.242026-06-0979482Update dependencies
0.9.232026-06-0278975Update dependencies
0.9.222026-06-0178537Add user-configurable num_workers concurrency setting (default 5, tested optimal at 7)
0.9.22-rc.22026-05-2778468Concurrency tuning iteration 2 — bump default_concurrency from 7 to 8
0.9.22-rc.12026-05-2678444Concurrency tuning — bump default_concurrency from 5 to 7 for progressive rollout
0.9.212026-04-2877407Update dependencies
0.9.202026-04-2176772Update dependencies
0.9.192026-03-3175797Update dependencies
0.9.182026-03-2475330Update dependencies
0.9.172026-03-1074601Update dependencies
0.9.162026-03-0373562Update dependencies
0.9.152026-02-0372578Update dependencies
0.9.142026-01-2072096Update dependencies
0.9.132026-01-1471517Update dependencies
0.9.122025-12-1870669Update dependencies
0.9.112025-11-2570115Update dependencies
0.9.102025-11-1869655Update dependencies
0.9.92025-10-2968882Update dependencies
0.9.82025-10-2268591Add suggestedStreams
0.9.72025-10-2168468Update dependencies
0.9.62025-10-1467945Update dependencies
0.9.52025-10-0767221Update dependencies
0.9.42025-09-3066859Update dependencies
0.9.32025-09-2466627Update dependencies
0.9.22025-09-0966114Update dependencies
0.9.12025-08-2465501Update dependencies
0.9.02025-08-2164879Update events stream to use start and query params instead of filtering on source side
0.8.172025-08-1064850Update dependencies
0.8.162025-08-0264455Update dependencies
0.8.152025-07-2663965Update dependencies
0.8.142025-07-2063667Update dependencies
0.8.132025-07-0562716Update dependencies
0.8.122025-06-2861458Update dependencies
0.8.112025-05-2460461Update dependencies
0.8.102025-05-1560295Fix missing records for events stream
0.8.92025-05-1060171Update dependencies
0.8.82025-05-0459571Update dependencies
0.8.72025-04-2758970Update dependencies
0.8.62025-04-1958446Update dependencies
0.8.52025-04-1257927Update dependencies
0.8.42025-04-0557473Update dependencies
0.8.32025-03-2956847Update dependencies
0.8.22025-03-2256263Update dependencies
0.8.12025-03-0855062Update dependencies
0.8.02025-03-0555215Fix lints for events stream
0.7.02025-02-2546664Converting to manifest-only format
0.6.112025-02-2254521Update dependencies
0.6.102025-02-1554100Update dependencies
0.6.92025-02-0853513Update dependencies
0.6.82025-02-0152979Update dependencies
0.6.72025-01-2552503Update dependencies
0.6.62025-01-1851896Update dependencies
0.6.52025-01-1151335Update dependencies
0.6.42025-01-0450930Update dependencies
0.6.32024-12-2850709Update dependencies
0.6.22024-12-2149058Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
0.6.12024-11-0443855Update dependencies
0.6.02024-10-3047988Upgrade the CDK and startup files to sync incremental streams concurrently
0.5.32024-06-0639180[autopull] Upgrade base image to v1.2.2
0.5.22024-05-2038263Replace AirbyteLogger with logging.Logger
0.5.12024-04-0136731Add %Y-%m-%dT%H:%M:%S%z to date time formats.
0.5.02024-03-2735755Migrate to low-code.
0.4.22024-03-2536448Unpin CDK version
0.4.12024-02-1235145Manage dependencies with Poetry
0.4.02024-01-0532957Added undeclared fields to schema and migrated to base image
0.3.02023-09-0530192Added undeclared fields to schema
0.2.42023-08-1429401Fix null value in stream state
0.2.32023-08-0329023Add incremental for issues stream
0.2.22023-05-0225759Change stream that used in check_connection
0.2.12023-04-2725602Add validation of project and organization names during connector setup
0.2.02023-04-0323923Add Releases stream
0.1.122023-03-0123619Fix bug when stream state is None or any other bad value occurs
0.1.112023-02-0222303Turn ON default AvailabilityStrategy
0.1.102023-01-2722041Set AvailabilityStrategy for streams explicitly to None
0.1.92022-12-2021864Add state persistence to incremental sync
0.1.82022-12-2020709Add incremental sync
0.1.72022-09-3017466Migrate to per-stream states
0.1.62022-08-2916112Revert back to the Python CDK
0.1.52022-08-2415911Bugfix to allowing reading schemas at runtime
0.1.42022-08-1915800Bugfix to allow reading sentry.yaml at runtime
0.1.32022-08-1715734Fix yaml based on the new schema validator
0.1.22021-12-2815345Migrate to config-based framework
0.1.12021-12-288628Update fields in source-connectors specifications
0.1.02021-10-126975New Source: Sentry
Was this page helpful?